This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/30241] New: __libc_stack_end is not portable between PPC distributions
- From: "hanwen at xs4all dot nl" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 17 Dec 2006 17:54:38 -0000
- Subject: [Bug other/30241] New: __libc_stack_end is not portable between PPC distributions
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
Hello,
i'm not sure this is the right place to report this. Please direct me elsewhere
if it's not.
I'm trying to build generic binaries for lilypond (lilypond.org), using a x86
pc targetting linux/ppc. I'm building a cross-compiler against the
Debian/stable libs/headers.
My problem is that libgcc_s.so links in the __libc_stack_end symbol
(ppc_linux_aux_vector () in config/rs6000/linux-unwind.h )
This symbol has differing versions across platforms (GLIB_2.1 on Fedora Core,
Yellow Dog Linux and GLIBC_PRIVATE on Debian/stable), so it's not possible to
build PPC binaries that run on all linux/ppc distributions.
I could try patching GCC sources, to simulate a stupid PPC CPU, but it would be
nice if this worked out of the box, ie. if ppc_fallback_frame_state() could
determine CPU characteristics without looking at __libc_stack_end.
--
Summary: __libc_stack_end is not portable between PPC
distributions
Product: gcc
Version: 4.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: hanwen at xs4all dot nl
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: powerpc-linux
GCC target triplet: powerpc-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30241