This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: A strange problem to compile glibc cvs ["Tue Dec 10 00:17:06 2002"] to ARM arch
- From: Ulrich Drepper <drepper at redhat dot com>
- To: "Hu, Boris" <boris dot hu at intel dot com>
- Cc: "'libc-alpha at sources dot redhat dot com'" <libc-alpha at sources dot redhat dot com>, "'NPT library mailing list'" <phil-list at redhat dot com>, "'Linux-Arm (E-mail)'" <linux-arm at lists dot arm dot linux dot org dot uk>
- Date: Wed, 15 Jan 2003 02:15:12 -0800
- Subject: Re: A strange problem to compile glibc cvs ["Tue Dec 10 00:17:06 2002"] to ARM arch
- Organization: Red Hat, Inc.
- References: <957BD1C2BF3CD411B6C500A0C944CA260216C332@pdsmsx32.pd.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hu, Boris wrote:
> collect2: ld terminated with signal 11 [Segmentation fault], core dumped
> /usr/local/arm-linux/arm-linux/bin/ld: Dwarf Error: Invalid or unhandled
> FORM value: 14.
> /usr/local/arm-linux/arm-linux/bin/ld: Dwarf Error: Invalid or unhandled
> FORM value: 14.
> [...]
I think you fail to understand the extend of the work *you* have to do
first before even thinking about an NPTL port to Arm.
A fundamental requirement for NPTL is an TLS ABI (see
http://people.redhat.com/drepper/tls.pdf). This in turn requires that
the Arm ABI finally gets a thread register. Once you have these
prerequisites you have to update all the tools (gcc + binutils) to
support the new ABI. After you have done all that you can finally start
porting NPTL.
The phil-list is no place to discuss the ABI and tools related problems.
So please don't post to phil-list any problem reports until you have a
fully functional toolchain.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+JTSx2ijCOnn/RHQRAsNZAKCAj7BXK2mgrWWQCeMJsvehm9KykgCgrF26
WK5dv0K+L4m9vgt5JqSCGbE=
=xC7u
-----END PGP SIGNATURE-----