Trying to build glibc x64 for cross-compiling on SPARC

Message

JFGI_123 · Post by **JFGI_123** » Fri Sep 03, 2010 1:56 pm

Have a couple of Sun boxes, fairly beefy, that I want some of the less powerful x86/x64 boxes to use when compiling

Got crossdev and done the x86 side. All working rather lovely

But can not get the x64 version of glibc to build on any of them (using "crossdev -t x86_64")

First things first. Is what I'm trying to do possible? or not possible for any reason? Should glibc just build without any problems?

If there isn't any reason why it shouldn't work, I'll post the error message

JFGI_123 · Post by **JFGI_123** » Thu Oct 21, 2010 11:02 am

ok, I'm going to assume it should work

so error I get in the build log is

/usr/libexec/gcc/x86_64-pc-linux-gnu/ld: /var/tmp/cross/x86_64-pc-linux-gnu/portage/cross-x86_64-pc-linux-gnu/glibc-2.12.1-r1/work/build-amd64-x86_64-pc-linux-gnu-nptl/libc_pic.os: TLS transition from R_X86_64_TLSGD to R_X86_64_GOTTPOFF against `__libc_resp' at 0xc2ac8 in section `.text' failed

/usr/libexec/gcc/x86_64-pc-linux-gnu/ld: final link failed: Bad value

Make sense to anyone?

alexbuell · Post by **alexbuell** » Thu Oct 21, 2010 12:04 pm

JFGI_123 wrote:ok, I'm going to assume it should work

so error I get in the build log is

/usr/libexec/gcc/x86_64-pc-linux-gnu/ld: /var/tmp/cross/x86_64-pc-linux-gnu/portage/cross-x86_64-pc-linux-gnu/glibc-2.12.1-r1/work/build-amd64-x86_64-pc-linux-gnu-nptl/libc_pic.os: TLS transition from R_X86_64_TLSGD to R_X86_64_GOTTPOFF against `__libc_resp' at 0xc2ac8 in section `.text' failed

/usr/libexec/gcc/x86_64-pc-linux-gnu/ld: final link failed: Bad value

Make sense to anyone?

Yeah, you're building unstable toolchains by using crossdev -t x86_64

1. crossdev -C x86_64 # to clear it all out
2. crossdev -S x86_64

That should build a *stable* toolchain for you.

JFGI_123 · Post by **JFGI_123** » Thu Oct 21, 2010 12:26 pm

cheers Alex,

I'll give it a go and see what happens

JFGI_123 · Post by **JFGI_123** » Thu Oct 21, 2010 1:18 pm

Ten Thousand Thundering Typhoons

Same problem

alexbuell · Post by **alexbuell** » Thu Oct 21, 2010 11:05 pm

JFGI_123 wrote:Ten Thousand Thundering Typhoons

Same problem

Hmm, is your box a multilibbed one i.e can it build both 32bit and 64 bit programs with GCC (not kgcc64?)

JFGI_123 · Post by **JFGI_123** » Fri Oct 22, 2010 1:08 pm

I do have support for x86 already on the box and had wondered if this was the reason why it was giving me issues. just haven't been bothered to remove the x86 libs to find out (and it's been working for other x86 boxes recently so it's in use)

However I do have another x86 which has libs for x64 and SPARC so thought it wouldn't be an issue to have x86 and x64 libs on the same SPARC box

alexbuell · Post by **alexbuell** » Fri Oct 22, 2010 3:45 pm

JFGI_123 wrote:I do have support for x86 already on the box and had wondered if this was the reason why it was giving me issues. just haven't been bothered to remove the x86 libs to find out (and it's been working for other x86 boxes recently so it's in use)

However I do have another x86 which has libs for x64 and SPARC so thought it wouldn't be an issue to have x86 and x64 libs on the same SPARC box

No, that's not what I meant. Is the native GCC compiler capable of building both 32bit and 64bit programs (not the cross comoilers)

bombsquad · Post by **bombsquad** » Mon Sep 19, 2011 8:57 pm

Any joy with this endeavour in the end?

I am attempting the same thing: build x86_64-pc-linux-gnu-gcc with crossdev running on sparc. glibc fails to build as the topic poster described; all versions of glibc in portage fail with some form of error including the one selected by crossdev -S.

My SPARC system is not multilibbed - userland is sparc - kernel is sparc64.

I can use the stage1 gcc (no CXX) that succeeds in building with distcc; ideally I want to use the full compiler with distcc too.

alexbuell · Post by **alexbuell** » Fri Apr 06, 2012 1:23 am

bombsquad wrote:Any joy with this endeavour in the end?

I am attempting the same thing: build x86_64-pc-linux-gnu-gcc with crossdev running on sparc. glibc fails to build as the topic poster described; all versions of glibc in portage fail with some form of error including the one selected by crossdev -S.

My SPARC system is not multilibbed - userland is sparc - kernel is sparc64.

I can use the stage1 gcc (no CXX) that succeeds in building with distcc; ideally I want to use the full compiler with distcc too.

I filed a bug for this ages ago which never been solved/resolved.

See https://bugs.gentoo.org/show_bug.cgi?id=361779

gentoo-freak · Post by **gentoo-freak** » Tue May 31, 2016 11:07 am

alexbuell wrote:
JFGI_123 wrote:ok, I'm going to assume it should work

so error I get in the build log is

/usr/libexec/gcc/x86_64-pc-linux-gnu/ld: /var/tmp/cross/x86_64-pc-linux-gnu/portage/cross-x86_64-pc-linux-gnu/glibc-2.12.1-r1/work/build-amd64-x86_64-pc-linux-gnu-nptl/libc_pic.os: TLS transition from R_X86_64_TLSGD to R_X86_64_GOTTPOFF against `__libc_resp' at 0xc2ac8 in section `.text' failed

/usr/libexec/gcc/x86_64-pc-linux-gnu/ld: final link failed: Bad value

Make sense to anyone?
Yeah, you're building unstable toolchains by using crossdev -t x86_64

1. crossdev -C x86_64 # to clear it all out
2. crossdev -S x86_64

That should build a *stable* toolchain for you.

Trying to build glibc x64 for cross-compiling on SPARC

Trying to build glibc x64 for cross-compiling on SPARC

nice hint