From: Tony Breeds <tony@bakeyournoodle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alex Chiang <achiang@hp.com>, Robin Holt <holt@sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org
Subject: Re: cross-compilers
Date: Fri, 10 Apr 2009 07:52:07 +1000 [thread overview]
Message-ID: <20090409215207.GN16602@bilbo.ozlabs.org> (raw)
In-Reply-To: <20090408174443.79e71503.akpm@linux-foundation.org>
On Wed, Apr 08, 2009 at 05:44:43PM -0700, Andrew Morton wrote:
> Please do.
linux-next is built on powerpc so I needed to rebuild many of the compilers for
intel.
While I was there I "updated to 4.3.3 and a 4.4.0 snapshot (20090216).
I've placed (well am placing):
x86_64 host, gcc 4.3.3, binutils 2.19.1:
alpha-linux
arm-linux
avr-linux
cris-linux
hppa64-linux
hppa-linux
i386-linux
m68k-linux
mipsel-linux
mips-linux
powerpc-linux
s390x-linux
sparc-linux
xtensa-linux
x86_64 host, gcc 4.4.0-20090216, binutils 2.19.1:
alpha-linux
arm-linux
avr-linux
cris-linux
hppa64-linux
i386-linux
m68k-linux
powerpc-linux
s390x-linux
sparc-linux
I haven't succeeded in builting a ia64 compiler, but I'll keep trying.
The i386,powerpc and sparc compilers are biarch and seem to build the 32/64
kernels appropriately.
I'm building i386 hosted compiiler ATM and I'll uplaod them when done.
Looking at the 4.3.3 compilers, asside from ia64 what arches are missing?
> Several people have made suggestions but I don't think I've yet seen
> anything which is download-and-go. Many of them appear to be ways of
> tricking people into installing distributions which include dselect,
> but I'm awake to their little games.
These should all be relocatable, in that you can wack them anywhere (/opt/cross
for me) and set your CROSS_COMPILE var and go.
For what it's worth these compilers were built with something derrived from
the buildall scripts by Segher (http://git.infradead.org/users/segher/buildall.git)
Thanks Segher!
Yours Tony
next prev parent reply other threads:[~2009-04-09 21:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 0:39 cross-compilers Alex Chiang
2009-04-08 1:03 ` cross-compilers Robin Holt
2009-04-08 5:46 ` cross-compilers Alex Chiang
2009-04-08 5:53 ` cross-compilers Pekka Enberg
2009-04-08 5:54 ` cross-compilers Andrew Morton
2009-04-08 6:12 ` cross-compilers Peter Chubb
2009-04-08 10:53 ` cross-compilers Matthew Wilcox
2009-04-08 15:29 ` cross-compilers Lennart Sorensen
2009-04-08 15:39 ` cross-compilers Xavier Bestel
2009-04-08 17:33 ` cross-compilers Alex Chiang
2009-04-08 17:36 ` cross-compilers Randy Dunlap
2009-04-09 12:52 ` cross-compilers Jan-Benedict Glaw
2009-04-09 20:51 ` cross-compilers Segher Boessenkool
2009-04-09 0:20 ` cross-compilers Rob Landley
2009-04-09 0:33 ` cross-compilers Tony Breeds
2009-04-09 0:44 ` cross-compilers Andrew Morton
2009-04-09 0:55 ` cross-compilers Alex Chiang
2009-04-09 20:24 ` cross-compilers Helge Deller
2009-04-09 20:31 ` cross-compilers Alex Chiang
2009-04-09 21:52 ` Tony Breeds [this message]
2009-04-09 23:47 ` cross-compilers Jan-Benedict Glaw
2009-04-10 10:12 ` cross-compilers Jan-Benedict Glaw
2009-04-10 10:19 ` cross-compilers Mike Frysinger
2009-04-10 10:49 ` cross-compilers Sam Ravnborg
2009-04-10 10:50 ` cross-compilers Mike Frysinger
2009-04-10 15:59 ` cross-compilers Jan-Benedict Glaw
2009-04-10 16:03 ` cross-compilers Al Viro
2009-04-11 11:23 ` cross-compilers Jan-Benedict Glaw
2009-04-10 5:45 ` cross-compilers Sam Ravnborg
2009-04-11 9:46 ` cross-compilers Tony Breeds
2009-04-09 7:29 ` cross-compilers Geert Uytterhoeven
2009-04-08 5:55 ` cross-compilers Robin Holt
2009-04-08 9:50 ` cross-compilers Andi Kleen
2009-04-08 11:08 ` cross-compilers Alex Buell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090409215207.GN16602@bilbo.ozlabs.org \
--to=tony@bakeyournoodle.com \
--cc=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=holt@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).