On 2020-03-13, Paul Eggert wrote:
> On 3/13/20 3:04 PM, Nick Bowler wrote:
>>AS_VAR_SET_IF([my_cv_no_printing], [my_cv_no_printing=hello])
>
> I assume you meant
>
>AS_VAR_SET_IF([my_cv_no_printing], [], [my_cv_no_printing=hello])
Yes, thank you for the correction.
Cheers,
Nick
On Fri, Mar 13, 2020 at 5:54 PM Bruno Haible wrote:
>
> [CCing autoc...@gnu.org]
>
> Hi Zack,
>
> > Abstractly, the best thing to do about this would be to remove the
> > macro and change all of its uses to be AC_CACHE_CHECK, with proper
> > messaging, instead.
>
> The point is that we don't want
Nick Bowler and Paul Eggert wrote:
> >AS_VAR_SET_IF([my_cv_no_printing], [my_cv_no_printing=hello])
>
>AS_VAR_SET_IF([my_cv_no_printing], [], [my_cv_no_printing=hello])
But then I lose
- the various AC_DIAGNOSE checks that are in AC_CACHE_VAL,
- possible future improvements / changes
On 3/13/20 3:04 PM, Nick Bowler wrote:
AS_VAR_SET_IF([my_cv_no_printing], [my_cv_no_printing=hello])
I assume you meant
AS_VAR_SET_IF([my_cv_no_printing], [], [my_cv_no_printing=hello])
Hi Bruno,
On 13/03/2020, Bruno Haible 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 occas
[CCing autoc...@gnu.org]
Hi Zack,
> Abstractly, the best thing to do about this would be to remove the
> macro and change all of its uses to be AC_CACHE_CHECK, with proper
> messaging, instead.
The point is that we don't want messaging for some tests. Most people
find the 'configure' output alre
I'm doing groundwork for the long-overdue release of autoconf 2.70,
and part of that is checking to make sure that various changes in
development trunk since 2.69 haven't broken third-party macros. I
noticed that gnulib-common.m4 contains a macro, gl_CACHE_VAL_SILENT,
that attempts to make AC_CACH
