Re: Can't build gcc-2.95.3 with g++ for m68k-elf

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

>>I did it in a parallel directory, as if it was a totally separate
>>package.
>
>Something like:
>
>[pbarada: ~/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc] > mkdir ../build-libiberty
>[pbarada: ~/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc] > cd ../build-libiberty/
>[pbarada: ~/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-libiberty] > /home/pbarada/work/cvs-wavemark/cross-linux-tools/g++-2.95.3/libiberty/configure --prefix=/tmp/crap-g++-2.95.3
>
>followed by 'make; make install' which ends up with:
>/tmp/crap-g++-2.95.3/lib/libiberty.a ???
>
>I'm trying to reconfigure and build the compiler now(after blowing away
>*everything* in the buld directory).

Grok.  That failed with:

cd ../libiberty ; make "SHELL=/bin/sh" "INSTALL=/bin/sh /home/pbarada/work/cvs-wavemark/cross-linux-tools/g++-2.95.3/install-sh -c" "INSTALL_DATA=/bin/sh /home/pbarada/work/cvs-wavemark/cross-linux-tools/g++-2.95.3/install-sh -c -m 644" "INSTALL_PROGRAM=/bin/sh /home/pbarada/work/cvs-wavemark/cross-linux-tools/g++-2.95.3/install-sh -c " "prefix=/tmp/crap-g++-2.95.3" "exec_prefix=/tmp/crap-g++-2.95.3" "tooldir=/tmp/crap-g++-2.95.3/m68k-elf" "gxx_include_dir=/tmp/crap-g++-2.95.3/include/g++-3" "libsubdir=/tmp/crap-g++-2.95.3/lib/gcc-lib/m68k-elf/2.95.3" "gcc_version=2.95.3" "gcc_version_trigger=/home/pbarada/work/cvs-wavemark/cross-linux-tools/g++-2.95.3/gcc/version.c" "AR=m68k-elf-ar" "AR_FLAGS=rc" "CC=/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/gcc/xgcc -B/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/gcc/ -B/tmp/crap-g++-2.95.3/m68k-elf/bin/" "CXX=/home/pbarada/work/cvs-wavemark/cross-linux!
!
!
-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/gcc/xgcc -B/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/gcc/ -B/tmp/crap-g++-2.95.3/m68k-elf/bin/" "CFLAGS=-g -O2" "CXXFLAGS=-g -O2" "NM=m68k-elf-nm" "RANLIB=m68k-elf-ranlib" "LIBCFLAGS=-g -O2" "LIBCXXFLAGS=-g -O2 -fno-implicit-templates" "LOADLIBES=" "LDFLAGS=" "MAKEINFO=/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/texinfo/makeinfo/makeinfo " "SHLIB=libstdc++.so.2.10.0" "SHCURSES=" "RUNTESTFLAGS="
make[2]: Entering directory `/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/m68k-elf/libiberty'
make[2]: *** No targets specified and no makefile found.  Stop.
make[2]: Leaving directory `/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/m68k-elf/libiberty'
make[1]: *** [../libiberty/libiberty.a] Error 2
make[1]: Leaving directory `/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/m68k-elf/libstdc++'
make: *** [all-target-libstdc++] Error 2


Here's the start of configure for build-gcc:

[pbarada: ~/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc] > /home/pbarada/work/cvs-wavemark/cross-linux-tools/g++-2.95.3/configure --target=m68k-elf --prefix=/tmp/crap-g++-2.95.3 --enable-languages=c,c++ --with-local-prefix=/tmp/crap-g++-2.95.3/m68k-elf 2>&1 | tee configure.log
Configuring for a i686-pc-linux-gnu host.
Created "Makefile" in /home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc
Configuring libiberty...
creating cache ../config.cache
checking host system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for ar... ar
checking for ranlib... ranlib
checking for gcc... gcc
checking whether we are using GNU C... yes

Note that in build-gcc/libiberty everything looks good.  Later on, I find:

Created "Makefile" in /home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/m68k-elf/libio/testsuite
Configuring in m68k-elf/libiberty
creating cache ./config.cache
checking host system type... m68k-unknown-elf
checking build system type... i686-pc-linux-gnu
checking for m68k-elf-ar... m68k-elf-ar
checking for m68k-elf-ranlib... m68k-elf-ranlib
checking for gcc... /home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/gcc/xgcc -B/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/gcc/ -B/tmp/crap-g++-2.95.3/m68k-elf/bin/
checking whether we are using GNU C... yes
checking whether /home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/gcc/xgcc -B/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k-elf/build-gcc/gcc/ -B/tmp/crap-g++-2.95.3/m68k-elf/bin/ accepts -g... yes
checking for POSIXized ISC... no

So it looks like configure thinks it has to configure
build-gcc/m68k-elf/libiberty which is bogus unless I'm making a
canadian cross(I think)....

Any more ideas?  Should I try --build=i686-pc-linux-gnu,
--target=m68k-elf, no --host=i686-pc-linux-gnu?  How does configure
determine if it needs to configure libiberty?

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

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com