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: 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: 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 >