Bug 84839

Summary:	Cross gcc build: USE flag "uclibc"???
Product:	Gentoo Linux	Reporter:	Klaus Kusche <Klaus.Kusche>
Component:	[OLD] GCC Porting	Assignee:	Please assign to toolchain <gcc-porting>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	High
Version:	2004.3
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description Klaus Kusche 2005-03-11 03:03:19 UTC

I'm trying to build a cross toolchain using gcc-3.4.3.20050110. 
The host is a Gentoo i686 with glibc, the target is an arm with uclibc.

I checked toolchain.eclass and found out that I must use the "uclibc" USE flag for building the cross compiler to get it configured with "--disable-__cxa_atexit" and "--enable-sjlj-exception". Otherwise, the code produced by the cross compiler will not run on the target system (it would be compiled for "--enable-__cxa_atexit", and I was told that this does not work on an uclibc system).

Now my question is:
Has compiling the cross gcc with USE="uclibc" any other side effects? 
Of course, it also causes the host parts of the gcc build (the compiler executables) to be built with USE="uclibc", which is wrong, because the host system uses glibc only, not uclibc, and hence the host executables should not be built for uclibc!

Comment 1 SpanKY gentoo-dev

2005-03-11 07:12:45 UTC

this has been fixed already in the toolchain.eclass

read it again

Comment 2 Klaus Kusche 2005-03-12 08:46:06 UTC

I've read it again.

As far as I got it now, I must *not* USE uclibc if the host uses glibc, but I must name my target "*-uclibc" to have the lib's compiled for uclibc.

Correct?