Trouble building gcc-3.0.4 on hp/ux

[Peter Barada <pbarada at mail dot wm dot sps dot mot dot com>]

I'm trying to build gcc-3.0.4 on an HP/UX machine, targeted for
m68k-elf, and it blows up compiling eh_alloc.cc:

/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/gcc/xgcc -B/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/gcc/ -nostdinc++ -L/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/src -L/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/src/.libs -nostdinc -B/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/newlib/ -isystem /local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/newlib/targ-include -isystem /local/pbarada/cvs-wavemark/cross-linux-tools/gcc-304/newlib/libc/include -B/opt/coldfish/gcc/m68k-elf/bin/ -B/opt/coldfish/gcc/m68k-elf/lib/ -isystem /opt/coldfish/gcc/m68k-elf/include -I/local/pbarada/cvs-wavemark/cross-linux-tools/gcc-304/libstdc++-v3/../gcc -I/local/pbarada/cvs-wavemark/cross-linux-tools/gcc-304/libstdc++-v3/../include -I/local/pbarada/cvs-wavemark/cross-linux-tools/obj!
!
!
/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/m68k-elf -I/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include -I/local/pbarada/cvs-wavemark/cross-linux-tools/gcc-304/libstdc++-v3/libsupc++ -g -O2 -fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings -Winline -fdiagnostics-show-location=once -g -c /local/pbarada/cvs-wavemark/cross-linux-tools/gcc-304/libstdc++-v3/libsupc++/eh_alloc.cc -o eh_alloc.o
In file included from /local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/cstdlib:31,
                 from /local/pbarada/cvs-wavemark/cross-linux-tools/gcc-304/libstdc++-v3/libsupc++/eh_alloc.cc:34:
/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/bits/std_cstdlib.h:75: `div_t'
   not declared
/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/bits/std_cstdlib.h:76: `ldiv_t'
   not declared
/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/bits/std_cstdlib.h:86: `div'
   not declared
/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/bits/std_cstdlib.h:91: `ldiv'
   not declared
/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/bits/std_cstdlib.h:93: `mblen'
   not declared
/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/bits/std_cstdlib.h:94: `mbstowcs'
   not declared
/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/bits/std_cstdlib.h:95: `mbtowc'
   not declared
/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/bits/std_cstdlib.h:104: `wcstombs'
   not declared
/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/bits/std_cstdlib.h:105: `wctomb'
   not declared
/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/include/bits/std_cstdlib.h:111: syntax
   error before `(' token
make[3]: *** [eh_alloc.lo] Error 1
make[3]: Leaving directory `/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3/libsupc++'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/local/pbarada/cvs-wavemark/cross-linux-tools/obj/coldfish/m68k-elf/gcc/m68k-elf/libstdc++-v3'
make: *** [all-target-libstdc++-v3] Error 2

What's really weird is when I compare what has been built to the same
build on a linux box, I find that on the hp/ux machine, there's a
munged version of stdlib.h:

[hpux m68k-elf/gcc] > find . -name stdlib.h
./gcc/include/stdlib.h
[hpux m68k-elf/gcc] >

but on the Linux machine there isn't:
[linux m68k-elf/gcc] > find . -name stdlib.h
[linux m68k-elf/gcc] >

If I remove ./gcc/include/stdlib.h, and continue, eh_alloc.cc builds
since it used the stdlib.h that came from newlib,  (and then blows up
later building pure.cc).

I'm a little confused over this since eh_alloc.cc is built using the
*cross* compiler, not the native gcc compiler, so why is it using the
includes files that were needed to construct the compiler, not the
runtime libraries?

-- 
Peter Barada                                   Peter.Barada@motorola.com
Wizard                                         781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola)   781-270-0193 (fax)