Bug#403628: ppc GCC links in __libc_stack_end, but defined as GLIBC_PRIVATE in ld-2.3.2.so
Package: libc6
Version: 2.3.2.ds1-22sarge4_powerpc.deb
I'm trying to build portable linux/PPC binaries, by linking against
libc6-2.3.2.ds1-22sarge4_powerpc.deb
libgcc_s.so (GCC 4.1) requires the __libc_stack_end symbol to discover
CPU features necessary for stack-unwinding, so all packages using
libgcc_s.so compiled with gcc 4.1 require __libc_stack_end.
Debian defines __libc_stack_end as GLIBC_PRIVATE, but on most other
platforms, I checked (Fedora Core 6, Yellow Dog 4.1, recent Ubuntu) it
has version GLIBC_2.1. This means that running such a binary results
in 'undefined symbol' errors.
The net result is that it is impossible to use stock gcc 4.1 to
produce C++ programs that run both on debian stable/ppc and YDL 4.1.
The GCC developers suggested I report this here.
See also http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30241
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
Reply to: