bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Nick Bowler <nbowler@draconx.ca>
To: Bruno Haible <bruno@clisp.org>
Cc: Zack Weinberg <zackw@panix.com>, autoconf@gnu.org, bug-gnulib@gnu.org
Subject: Re: gl_CACHE_VAL_SILENT won't work correctly with upcoming autoconf 2.70
Date: Fri, 13 Mar 2020 18:04:23 -0400	[thread overview]
Message-ID: <CADyTPEzQARtzUYV12sYv_gRsj_caGmzv_q1L3gFu3fjTk1WafQ@mail.gmail.com> (raw)
In-Reply-To: <1867344.WzrmtSNFgT@omega>

Hi Bruno,

On 13/03/2020, Bruno Haible <bruno@clisp.org> wrote:
> The underlying problem in Autoconf is the following: There is a macro
> AC_CACHE_CHECK that does messaging, and a macro AC_CACHE_VAL whose
> main purpose is to make a cache lookup, not messaging, but it
> nevertheless outputs '(cached)' strings occasionally.
>
> Please fix this correctly
[...]
>   - or by introducing a macro that is like AC_CACHE_VAL but produces
>     no spurious output.

Such a macro already exists in Autoconf.  If you do not need the
messaging from AC_CACHE_VAL you can simply use AS_VAR_SET_IF.

For example:

  AS_VAR_SET_IF([my_cv_no_printing], [my_cv_no_printing=hello])

You could also just write a normal shell if statement.

Cheers,
  Nick


  reply	other threads:[~2020-03-13 22:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 20:57 gl_CACHE_VAL_SILENT won't work correctly with upcoming autoconf 2.70 Zack Weinberg
2020-03-13 21:54 ` Bruno Haible
2020-03-13 22:04   ` Nick Bowler [this message]
2020-03-13 23:30     ` Paul Eggert
2020-03-14  0:27       ` Bruno Haible
2020-03-14  1:27       ` Nick Bowler
2020-03-14  1:11   ` Zack Weinberg
2020-03-14  2:49     ` debugging autoconf tests (was: gl_CACHE_VAL_SILENT) Bruno Haible
2020-03-14 14:06       ` Zack Weinberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADyTPEzQARtzUYV12sYv_gRsj_caGmzv_q1L3gFu3fjTk1WafQ@mail.gmail.com \
    --to=nbowler@draconx.ca \
    --cc=autoconf@gnu.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=zackw@panix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).