Re: incorrect caching messages

2006-11-15 Thread Ralf Wildenhues
Hello Paul, Bruno, * Paul Eggert wrote on Wed, Nov 15, 2006 at 09:54:19PM CET: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > The allocsa.m4 change contradicts > > http://lists.gnu.org/archive/html/bug-gnulib/2006-10/msg00279.html > > I don't see why it's contradictory. * Bruno Haible wrot

Re: [bug-gnulib] incorrect caching messages

2006-11-15 Thread Bruno Haible
Ralf Wildenhues wrote: > The allocsa.m4 change contradicts > http://lists.gnu.org/archive/html/bug-gnulib/2006-10/msg00279.html The URL is very relevant (I was tempted to use AC_REQUIRE, nearly falling into the pitfall again), thanks. But I don't actually see the contradiction. Bruno

Re: [bug-gnulib] incorrect caching messages

2006-11-15 Thread Bruno Haible
Eric Blake wrote: > --- m4/alloca.m4 20 Oct 2006 13:50:26 - 1.8 > +++ m4/alloca.m4 15 Nov 2006 17:00:14 - > @@ -1,4 +1,4 @@ > -# alloca.m4 serial 6 > +# alloca.m4 serial 7 > dnl Copyright (C) 2002-2004, 2006 Free Software Foundation, Inc. > dnl This file is free software; t

Re: incorrect caching messages

2006-11-15 Thread Paul Eggert
Ralf Wildenhues <[EMAIL PROTECTED]> writes: > The allocsa.m4 change > contradicts > http://lists.gnu.org/archive/html/bug-gnulib/2006-10/msg00279.html I don't see why it's contradictory. That URL says that gl_ALLOCSA should not AC_REQUIRE gl_FUNC_ALLOCA. But the proposed allocsa.m4 change: >>

Re: [bug-gnulib] incorrect caching messages

2006-11-15 Thread Bruno Haible
Eric Blake wrote: > 2006-11-15 Eric Blake <[EMAIL PROTECTED]> > > * m4/allocsa.m4 (gl_ALLOCSA): Don't invoke macro already picked > up by the module dependency. > > Index: m4/allocsa.m4 > === > RCS file: /sources/gnulib

Re: incorrect caching messages

2006-11-15 Thread Ralf Wildenhues
Hello Eric, * Eric Blake wrote on Wed, Nov 15, 2006 at 06:02:00PM CET: > > checking for intmax_t... (cached) yes > (cached) (cached) checking whether to enable assertions... no > > I tracked both of those spurious messages to this. gl_ALLOCSA was calling > gl_FUNC_ALLOCA rather than AC_REQUIRE

Re: incorrect caching messages

2006-11-15 Thread Eric Blake
Paul Eggert CS.UCLA.EDU> writes: > > 2006-11-15 Eric Blake byu.net> > > > > * m4/alloca.m4 (gl_FUNC_ALLOCA): Use AC_CACHE_CHECK to avoid a > > random "(cached)" in configure output. > > * m4/allocsa.m4 (gl_ALLOCSA): Don't invoke macro already picked > > up by the module depende

Re: incorrect caching messages

2006-11-15 Thread Paul Eggert
Eric Blake <[EMAIL PROTECTED]> writes: > OK to install? > > 2006-11-15 Eric Blake <[EMAIL PROTECTED]> > > * m4/alloca.m4 (gl_FUNC_ALLOCA): Use AC_CACHE_CHECK to avoid a > random "(cached)" in configure output. > * m4/allocsa.m4 (gl_ALLOCSA): Don't invoke macro already picked >

incorrect caching messages

2006-11-15 Thread Eric Blake
Currently, when rerunning the m4 configure script with caching enabled, this output is appearing: checking for intmax_t... (cached) yes (cached) (cached) checking whether to enable assertions... no I tracked both of those spurious messages to this. gl_ALLOCSA was calling gl_FUNC_ALLOCA rather