------- Comment #1 from rob1weld at aol dot com 2007-05-25 10:49 -------
Found an additional problem.
After all the stages are done and we are building the libraries in the "target
name directory" (EG: in _my_ case the directory is called "i686-pc-linux-gnu")
we must _always_ use "xgcc" and NOT "gcc" (the OS's compiler).
Correct?
Here is a bit of screen output:
make[2]: Leaving directory `/opt/gcc-4_3-build/i686-pc-linux-gnu/boehm-gc'
make[2]: Entering directory `/opt/gcc-4_3-build/i686-pc-linux-gnu/libobjc'
: make ; exec true "AR=ar" "AR_FLAGS=rc" "CC=/opt/gcc-4_3-build/./gcc/xgcc
-B/opt/gcc-4_3-build/./gcc/ -B/usr/i686-pc-linux-gnu/bin/
-B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include -isystem
/usr/i686-pc-linux-gnu/sys-include" "CFLAGS=-O2 -g -O2 " "DESTDIR="
"LIBCFLAGS=-O2 -g -O2 " "EXTRA_OFILES="
That is OK.
Here is some more (from the build log):
# grep -A 4
/opt/gcc-4_3-build/i686-pc-linux-gnu/libjava/classpath/native/fdlibm
gcc-4_3-build/make_6*
gcc-4_3-build/make_6b_log.txt:make[5]: Entering directory
`/opt/gcc-4_3-build/i686-pc-linux-gnu/libjava/classpath/native/fdlibm'
gcc-4_3-build/make_6b_log.txt-if /bin/sh ../../libtool --mode=compile gcc
-DHAVE_CONFIG_H -I.
-I/root/downloads/gcc-4_3-trunk/libjava/classpath/native/fdlibm -I../../include
-O2 -g -O2 -MT dtoa.lo -MD -MP -MF ".deps/dtoa.Tpo" -c -o dtoa.lo
/root/downloads/gcc-4_3-trunk/libjava/classpath/native/fdlibm/dtoa.c; \
gcc-4_3-build/make_6b_log.txt- then mv -f ".deps/dtoa.Tpo" ".deps/dtoa.Plo";
else rm -f ".deps/dtoa.Tpo"; exit 1; fi
gcc-4_3-build/make_6b_log.txt-mkdir .libs
gcc-4_3-build/make_6b_log.txt-gcc -DHAVE_CONFIG_H -I.
-I/root/downloads/gcc-4_3-trunk/libjava/classpath/native/fdlibm -I../../include
-O2 -g -O2 -MT dtoa.lo -MD -MP -MF .deps/dtoa.Tpo -c
/root/downloads/gcc-4_3-trunk/libjava/classpath/native/fdlibm/dtoa.c -fPIC
-DPIC -o .libs/dtoa.o
Notice that is uses "gcc" to build dtoa ...
When I compiled gcc previously it didn't do that:
# grep -A 4
/opt/gcc-4_3-build/i686-pc-linux-gnu/libjava/classpath/native/fdlibm make_5*
make_5c_log.txt:make[5]: Entering directory
`/opt/gcc-4_3-build/i686-pc-linux-gnu/libjava/classpath/native/fdlibm'
make_5c_log.txt-if /bin/sh ../../libtool --mode=compile
/opt/gcc-4_3-build/./gcc/xgcc -B/opt/gcc-4_3-build/./gcc/
-B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem
/usr/i686-pc-linux-gnu/include -isystem /usr/i686-pc-linux-gnu/sys-include
-DHAVE_CONFIG_H -I.
-I/root/downloads/gcc-4_3-trunk/libjava/classpath/native/fdlibm -I../../include
-O2 -g -O2 -MT dtoa.lo -MD -MP -MF ".deps/dtoa.Tpo" -c -o dtoa.lo
/root/downloads/gcc-4_3-trunk/libjava/classpath/native/fdlibm/dtoa.c; \
make_5c_log.txt- then mv -f ".deps/dtoa.Tpo" ".deps/dtoa.Plo"; else rm
-f ".deps/dtoa.Tpo"; exit 1; fi
make_5c_log.txt-mkdir .libs
make_5c_log.txt-/opt/gcc-4_3-build/./gcc/xgcc -B/opt/gcc-4_3-build/./gcc/
-B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem
/usr/i686-pc-linux-gnu/include -isystem /usr/i686-pc-linux-gnu/sys-include
-DHAVE_CONFIG_H -I.
-I/root/downloads/gcc-4_3-trunk/libjava/classpath/native/fdlibm -I../../include
-O2 -g -O2 -MT dtoa.lo -MD -MP -MF .deps/dtoa.Tpo -c
/root/downloads/gcc-4_3-trunk/libjava/classpath/native/fdlibm/dtoa.c -fPIC
-DPIC -o .libs/dtoa.o
That is not the only library where this occurs. The tests will be invalid if
gcc is used instead of xgcc. The gcc-bugs scripts will be sending out false
e-mails about breakages.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32078
