Hi,
   attemting to build a i386 release from OS X fails in gcc. The full log is
   available at ftp://asim.lip6.fr/outgoing/build-i386.log, but basically
   the issue is:
   #   compile  backend/ggc-none.lo
   cc -O3 -mtune=G5 -mcpu=G5 -I. -I/Volumes/data/bouyer/current/src/gnu/usr.bin/gcc4/backend/../arch/i386 -DIN_GCC -DHAVE_CONFIG_H -I/Volumes/data/bouyer/curre
nt/src/gnu/dist/gcc4/gcc -I/Volumes/data/bouyer/current/src/gnu/dist/gcc4/gcc/. -I/Volumes/data/bouyer/current/src/gnu/dist/gcc4/gcc/../include -I/Volumes/data
/bouyer/current/src/gnu/dist/gcc4/gcc/../libcpp/include -I/Volumes/data/bouyer/current/src/gnu/usr.bin/gcc4/backend/.. -c -o ggc-none.lo.o    /Volumes/data/bou
yer/current/src/gnu/dist/gcc4/gcc/ggc-none.c
   In file included from /Volumes/data/bouyer/current/src/gnu/dist/gcc4/gcc/ggc-none.c:32:
   /Volumes/data/bouyer/current/src/gnu/dist/gcc4/gcc/system.h:396:20: malloc.h: No such file or directory
   *** [ggc-none.lo] Error code 1
   1 error
   
   nbmake: stopped in /Volumes/data/bouyer/current/src/gnu/usr.bin/gcc4/backend
   *** [dependall-backend] Error code 2
   1 error
   
   nbmake: stopped in /Volumes/data/bouyer/current/src/gnu/usr.bin/gcc4
   
   
   As you can see it's using HOST_CC here, when is should be using the cross
   toolchain (building the cross-compiler has been done at this point, we're
   building the gcc binaries part of the comps.tgz set)


actually, this is right.  to build the (native) compiler you have to 
build a bunch of helper programs, and those have to run on the build
system.  so it should be using HOST_CC here.  the quesion is why is
this failing?  this should be using the "auto-build.h" that is created
by running configure and it should define/undef HAVE_MALLOC_H.


can you find out why that is occuring?  actually, this should be
compiled with -DGENERATOR_FILE...  let me check.