sh4 problem: "/lib/ no version information available"

Dan Kegel
Tue Jun 17 19:50:00 GMT 2003

I'm slowly making progress adding regression testing to my
crosstool script.  This morning I figured out why my ftpd
wouldn't run in my glibc-2.2.5 chroot environment on sh4:
getpwnam() was failing because couldn't
be loaded.  A little quick surgery on ftpd cured that :-)
and I'm sure I'll figure out the problem later.

Now a "hello, world" written in C runs fine in the chroot jail,
but one written in C++ fails with errors:

/result/sh4-unknown-linux-gnu/gcc-3.3-glibc-2.2.5/tmp$ ftp   (and put sh4-unknown-linux-gnu-hello2)
/result/sh4-unknown-linux-gnu/gcc-3.3-glibc-2.2.5/tmp$ rsh chmod +x sh4-unknown-linux-gnu-hello2
/result/sh4-unknown-linux-gnu/gcc-3.3-glibc-2.2.5/tmp$ rsh ./sh4-unknown-linux-gnu-hello2
./sh4-unknown-linux-gnu-hello2: /lib/ no version information available (required by ./sh4-unknown-linux-gnu-hello2)
./sh4-unknown-linux-gnu-hello2: /lib/ no version information available (required by /lib/
./sh4-unknown-linux-gnu-hello2: /lib/ no version information available (required by /lib/
./sh4-unknown-linux-gnu-hello2: relocation error: /lib/ symbol cosh, version GLIBC_2.2 not defined in file with link time reference

Oddly enough, objdump -p shows that there is indeed no version info
in built for sh4-unknown-linux-gnu/gcc-3.3-glibc-2.2.5
or sh4-unknown-linux-gnu/gcc-3.3-glibc-2.3.2, though there is version
info in that file for the other five architectures I built (i686, ppc, sparc, mipsel, cris).

Obviously I'm either building wrong, or there's
a bug in how it's built on sh4.  Has anyone run into this?

I'm using the vanilla build scripts at
and am not using most of the patches provided by the linux-sh project,
since there are quite a few and I'm trying to only apply patches
once I understand what they're for.  I did look through all the
patches in
but didn't see anything obviously related to libstdc++.

Suggestions welcome...


Dan Kegel

Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

More information about the crossgcc mailing list