final observation on failure to build SH toolchain

["Robert P. J. Day" <rpjday at mindspring dot com>]

  ok, here's my last post on the subject since i'm pretty sure i've
exhausted my knowledge on the subject.  the bug report is here:

  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24445

but that talks about trying to build for SH4.  turns out, i didn't
even need to push it that far -- i can get a build error building for
SH3 just from what comes with crosstool-0.38 and a gcc-4.1 snapshot.

  here's a combination that *works* for SH3 (that is, it at least
completes building a toolchain and the test succeeds):

BINUTILS_DIR=binutils-2.16.1
GCC_DIR=gcc-4.0.1
GLIBC_DIR=glibc-2.3.5
LINUX_SANITIZED_HEADER_DIR=linux-libc-headers-2.6.12.0
GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.3.5

TARGET=sh3-unknown-linux-gnu
TARGET_CFLAGS="-O -m3 -ml"
GLIBC_CONFIGPARMS="no-z-defs=yes"
GLIBC_EXTRA_CONFIG="--without-fp"
USE_SYSROOT=1

  now, all i have to do is make the following change and use an early
gcc-4.1 snapshot"

GCC_DIR=gcc-4.1-20050702

which generates the error:

/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/build-gcc/./gcc/xgcc
-shared-libgcc
-B/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/build-gcc/./gcc/
-nostdinc++
-L/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/build-gcc/sh3-unknown-linux-gnu/libstdc++-v3/src
-L/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/build-gcc/sh3-unknown-linux-gnu/libstdc++-v3/src/.libs
-B/home/rpjday/ct/sh3/sh3-unknown-linux-gnu/bin/
-B/home/rpjday/ct/sh3/sh3-unknown-linux-gnu/lib/ -isystem
/home/rpjday/ct/sh3/sh3-unknown-linux-gnu/include -isystem
/home/rpjday/ct/sh3/sh3-unknown-linux-gnu/sys-include
-I/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/build-gcc/sh3-unknown-linux-gnu/libstdc++-v3/include/sh3-unknown-linux-gnu
-I/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/build-gcc/sh3-unknown-linux-gnu/libstdc++-v3/include
-I/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/gcc-4.1-20050702/libstdc++-v3/libsupc++
-g -O2 -D_GNU_SOURCE -fno-implicit-templates -Wall -Wextra
-Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once
-ffunction-sections -fdata-sections
-I/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/build-gcc/sh3-unknown-linux-gnu/libstdc++-v3/include/backward
-Wno-deprecated -c
/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/gcc-4.1-20050702/libstdc++-v3/src/strstream.cc
-fPIC -DPIC -o .libs/strstream.o
/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/gcc-4.1-20050702/libstdc++-v3/src/strstream.cc:
In member function 'void
std::strstream::_ZTv0_n12_NSt9strstreamD0Ev()':
/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/gcc-4.1-20050702/libstdc++-v3/src/strstream.cc:415:
internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[3]: *** [strstream.lo] Error 1
make[3]: Leaving directory
`/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/build-gcc/sh3-unknown-linux-gnu/libstdc++-v3/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/build-gcc/sh3-unknown-linux-gnu/libstdc++-v3'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/rpjday/ct/crosstool-0.38/build/sh3-unknown-linux-gnu/gcc-4.1-20050702-glibc-2.3.5/build-gcc/sh3-unknown-linux-gnu/libstdc++-v3'
make: *** [all-target-libstdc++-v3] Error 2


  not even the same error, but it does show that even an early gcc-4.1
snapshot is not building for SH3.  sigh.

rday

p.s.  i can get a build using gcc-4.0.2 as well as gcc-4.0.1, so it's
clearly something that was introduced on the way to gcc-4.1.

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