Sparc64 Glibc 2.4 Build issue

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Sparc64 Glibc 2.4 Build issue

Jim Gifford
GCC 4.10 - Binutils 2.16.92 - Glibc 2.4

When cross-compiling GLIBC 2.4, everything build ok, but when we build
for the final-system build, we run into this strange error.

/tools/lib/gcc/sparc64-unknown-linux-gnu/4.1.0/../../../../sparc64-unknown-linux-gnu/bin/ld: Register %g7 used incompatibly: #scratch in /usr/src/glibc-64bit/nscd/dbg_log.o, previously __thread_self in /usr/src/glibc-64bit/nscd/nscd.o
/usr/src/glibc-64bit/nscd/dbg_log.o: could not read symbols: File format not recognized

Now adding <include "tls.h"> to dbg_log.c fixes the issue.

I have compared both builds of nscd and both configs from the build, and I can't see where the
the difference occurs.

I have the posted at
http://ftp.jg555.com/errors/cross for the cross-compiled - (config and nscd)
and
http://ftp.jg555.com/errors/native for the build that fails

I've done several builds on other architectures, with no problems, just Sparc seems to be an issue
with this configuration.

Any suggestions or ideas. I have both systems at the ready to test things out.

Reply | Threaded
Open this post in threaded view
|

Re: Sparc64 Glibc 2.4 Build issue

Jakub Jelinek
On Sat, Apr 29, 2006 at 03:54:02PM -0700, Jim Gifford wrote:
> GCC 4.10 - Binutils 2.16.92 - Glibc 2.4
>
> When cross-compiling GLIBC 2.4, everything build ok, but when we build
> for the final-system build, we run into this strange error.
>
> /tools/lib/gcc/sparc64-unknown-linux-gnu/4.1.0/../../../../sparc64-unknown-linux-gnu/bin/ld: Register %g7 used incompatibly: #scratch in /usr/src/glibc-64bit/nscd/dbg_log.o, previously __thread_self in /usr/src/glibc-64bit/nscd/nscd.o
> /usr/src/glibc-64bit/nscd/dbg_log.o: could not read symbols: File format
> not recognized

http://gcc.gnu.org/ml/gcc-patches/2006-02/msg00177.html

        Jakub
Reply | Threaded
Open this post in threaded view
|

Re: Sparc64 Glibc 2.4 Build issue

Jim Gifford
Jakub,
    That fixed the issue thank you!