84832 – Building cross gcc: Target CFLAGS?

Bug 84832 - Building cross gcc: Target CFLAGS?

Summary: Building cross gcc: Target CFLAGS?

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] GCC Porting (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Please assign to toolchain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-03-11 02:29 UTC by Klaus Kusche
Modified:	2005-06-10 23:58 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Klaus Kusche 2005-03-11 02:29:32 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.

When building the cross gcc, I found no way to specify different CFLAGS for the compilation of the host parts (compiler executables) and the target parts (libgcc, the Java libs, ...) of the gcc build.

I checked the log: The host parts are built with my make.cong CFLAGS, the target parts are using *default* CFLAGS (which is bad, I need to specify the arm processor type etc.!).

I think the native gcc build understands LIBCFLAGS or LIBGCC2_CFLAGS for that purpose (I don't know exactly which one), but how do I specifiy them when using emerge?

Comment 1 Wojciech Potentas 2005-05-25 23:24:37 UTC

Is there any "portage" way to add updatetable cross-compilers? For example to
distcc through i586, i686 and amd64?

Comment 2 SpanKY gentoo-dev

2005-06-10 16:46:04 UTC

you can already script around this, no need to added more complexity

Comment 3 Klaus Kusche 2005-06-10 23:58:00 UTC

?

Was comment #2 for my original problem or for comment #1?

What do you mean by "you can already script around this"?