recent patch broke bootstrap
Daniel Jacobowitz
drow@mvista.com
Sun Sep 7 18:41:00 GMT 2003
On Thu, Sep 04, 2003 at 08:12:20PM -0500, Loren James Rittle wrote:
>
> >> gcc-build-latour-mainline-0826/gcc/auto-host.h:/* #undef HAVE_MALLOC_H */
> >> gcc-build-latour-mainline-0903/gcc/auto-host.h:#define HAVE_MALLOC_H 1
>
> > Does libiberty also find malloc.h as usable, and did it before?
> > Libiberty converted to autoconf 2.57 in that window.
>
> Ah, thank you for that tidbit. Yes, it flipped detection status that
> same week:
>
> gcc-build-latour-mainline-0826/libiberty/config.h:/* #undef HAVE_MALLOC_H */
>
> configure:3633: checking for malloc.h
> configure:3638: result: no
>
> gcc-build-latour-mainline-0903/libiberty/config.h:#define HAVE_MALLOC_H 1
>
> configure:3642: checking malloc.h usability
> configure:3655: /usr/bin/gcc -c -g -O2 conftest.c >&5
> In file included from configure:3700:
> /usr/include/malloc.h:2: warning: #warning "this file includes <malloc.h> which
> is deprecated, use <stdlib.h> instead"
> configure:3658: $? = 0
> configure:3661: test -s conftest.o
> configure:3664: $? = 0
> configure:3674: result: yes
> configure:3678: checking malloc.h presence
> configure:3689: /usr/bin/gcc -E conftest.c
> In file included from configure:3702:
> /usr/include/malloc.h:2: warning: #warning "this file includes <malloc.h> which
> is deprecated, use <stdlib.h> instead"
> configure:3695: $? = 0
> configure:3714: result: yes
> configure:3750: checking for malloc.h
> configure:3757: result: yes
>
> autoconf used to treat any stderr output as failure during these tests
> (which were all packed together as one "usability/suitability" test).
> The correct solution would appear to be to force autoconf to check for
> header usability with -Werror, if our software itself must also build
> with that switch. I believe that FreeBSD is not the only system in
> existence to warn on inclusion of archaic headers which should no
> longer be used. Anyone know how to make it happen with the new
> autoconf?
I've poked the autoconf developers about this. Let's see what they
say.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
More information about the Gcc-patches
mailing list