Bug 17120 – cross-gcc-3.2.[12] , cross-binutils-2.13.*, cross-glibc-2.3

• Status: RESOLVED DUPLICATE of bug 18034
• Product: Gentoo Linux

[Description Zhen Lin 2003-03-08 22:45:24 UTC]

Will include ebuild tarballs. These ebuilds may unmerge native-gcc,
native-binutils or native-glibc, so only check the compile and install stages,
do not actually merge. Use CCHOST to define target architecture. This does not
apply architecture specific fixes, I do not know how to force it to.

Reproducible: Always
Steps to Reproduce:





Tested with CCHOST=i686-pc-gnu

[Comment 1 Zhen Lin 2003-03-08 22:46:56 UTC]

Created attachment 9148 [details]
cross-gcc

gcc-3.2.1-r6 and gcc-3.2.2

[Comment 2 Zhen Lin 2003-03-08 22:48:36 UTC]

Created attachment 9149 [details]
cross-binutils

binutils-2.13.90.0.16-r1
binutils-2.13.90.0.18

[Comment 3 Zhen Lin 2003-03-08 22:49:51 UTC]

Created attachment 9151 [details]
cross-glibc

glibc-2.3.1-r2

[Comment 4 Martin Schlemmer (RETIRED) 2003-03-09 00:16:37 UTC]

First I think diff between flags to ./configure should rather be added to
$myconf, than dupping the whole ./configure thing.

Then, any possibility to do a diff to latest gcc-3.2.2-r1 ... please check
I did some mods to the pkg_postinst and added pkg_preinst() ...

Zach ?

[Comment 5 James Boddington (RETIRED) 2003-03-13 01:27:21 UTC]

This is along the lines of what I am working on at 
http://cvs.gentoo.org/~aiken/gentoo-cross/ 
I have a set of ebuilds that will build a cross compiler tool chain for several 
architectors. Doing an emerge unmerge afterwards works cleanly as well. 
 
Zach is also doing a lot towards cross compiling at http://cvs.gentoo.org/~zwelch/ 
including Arm. 
 
There is quite a bit on information on both sites. 

[Comment 6 Martin Schlemmer (RETIRED) 2003-03-14 00:04:53 UTC]

Right.  The whole idea at the end of the day should be to have it very transparent
with switching done via gcc-config. Zach have done work in this regards towards
getting binutils, etc to work with that.

It will also be nice to have some sort of support added to portage for this,
so that it will not be needed to change things global for cross-compiling.

[Comment 7 James Boddington (RETIRED) 2003-03-14 03:09:39 UTC]

I can switch via gcc-config  gcc -v        identifies as i686-pc-unknown-linux 3.2.2 gcc-config sparc-uknown-linux-gnu-3.2.2 gcc -v        now identifies as sparc-unknown-linux-gnu 3.2.2 gcc-config i686-pc-linux-gnu-3.2.2 gcc -v        identifies as the i686 compiler again  This works with the 6 cross compilers I currently have installed. 

[Comment 8 Zach Welch (RETIRED) 2003-04-07 19:21:55 UTC]

The latest effort to integrate cross-compiling ebuilds into portage have
appeared in bugs 18031 through 18034.  These ebuilds, coupled with cross-gcc
or gcc-config (referenced in bug 18936), can provide complete toolchains for
multiple targets.  We are working to complete these, but I am going to mark
this bug as a duplicte in the meantime.  Please focus any comments or 
suggestions in these new bugs.  Thanks.

*** This bug has been marked as a duplicate of 18034 ***