Bug#403628: marked as done (ppc GCC links in __libc_stack_end, but defined as GLIBC_PRIVATE in ld-2.3.2.so)
Your message dated Tue, 19 Dec 2006 08:04:57 +0100
with message-id <45878F19.2070002@aurel32.net>
and subject line Bug#403628: ppc GCC links in __libc_stack_end, but defined as GLIBC_PRIVATE in ld-2.3.2.so
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Han-Wen Nienhuys a écrit :
> 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.
>
Sarge (and glibc 2.3.2) does not support gcc-4.1, though it is possible
get it working on some architectures.
If you want to have gcc-4.1, please upgrade to Etch (testing), or uses
at least the glibc from this distribution, it has all the necessary symbols.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
--- End Message ---
Reply to: