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_________________I.T. is like a box of chocolates on a hot day.....sticky

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)_________________Cheers,
Alex.

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 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.