Re: AC_FUNC_ALLOCA shouldn't define prototype

On 08/05/2010 02:36 PM, Paul Eggert wrote: > On 08/05/10 04:26, Bruno Haible wrote: > >> -char *alloca (); >> +void *alloca (); > > Thansks, I like this change too. Can you please install it? I also added the size_t argument to the prototype, then applied it. -- Eric Blake ebl...@redhat.com

Re: AC_FUNC_ALLOCA shouldn't define prototype

On 08/05/10 04:26, Bruno Haible wrote: > -char *alloca (); > +void *alloca (); Thansks, I like this change too. Can you please install it?

Re: AC_FUNC_ALLOCA shouldn't define prototype

Joerg Sonnenberger wrote: > > So, I don't understand how you see a "conflict". > > The conflicting declarations are a result of the default namespace > containing _NETBSD_SOURCE if no (other) standard compliance macro is > set. Still, I don't see how you can get a conflict with if the test code

Re: AC_INIT regression not completely fixed

On 08/05/2010 02:08 AM, Yavor Doganov wrote: > Seen while bootstrapping GNOME with 2.67: > > cat > configure.ac < AC_INIT([GNOME Foo], [2.31.6], > [http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-foo], > [gnome-foo]) > AC_OUTPUT > EOF > > autoconf > configure.ac:1: warning: AC_I

AC_INIT regression not completely fixed

Seen while bootstrapping GNOME with 2.67: cat > configure.ac

Re: AC_FUNC_ALLOCA shouldn't define prototype

Eric Blake wrote: > Rather than hard-code the check based on platform-specific defines, it > would be more in the autoconf spirit to instead write a probe whether > declares alloca(), and if so, define a witness macro. Unfortunately, the code is also used in bison/data/yacc.c [1], that is, in the