From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Andrew Morton <akpm@linux-foundation.org>,
Alex Chiang <achiang@hp.com>, Robin Holt <holt@sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: cross-compilers
Date: Fri, 10 Apr 2009 12:12:20 +0200 [thread overview]
Message-ID: <20090410101220.GF7921@lug-owl.de> (raw)
In-Reply-To: <20090409234750.GE7921@lug-owl.de>
[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]
On Fri, 2009-04-10 01:47:50 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> On Fri, 2009-04-10 07:52:07 +1000, Tony Breeds <tony@bakeyournoodle.com> wrote:
> > 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.
>
> I've started a build-bot like script for binutils + GCC from CVS/GIT.
> If it builds through, I'll start uploading i686 hosted compilers
> later on today.
So... I've now build trunk kernel-only cross-compilers (hosted on
i686) for these targets:
alpha-linux.tar.bz2
am33_2.0-linux.tar.bz2
arm-linux.tar.bz2
avr-linux.tar.bz2
bfin-uclinux.tar.bz2
cris-linux.tar.bz2
frv-linux.tar.bz2
h8300-elf.tar.bz2
hppa64-linux.tar.bz2
hppa-linux.tar.bz2
i386-linux.tar.bz2
ia64-linux.tar.bz2
m32r-linux.tar.bz2
m68k-linux.tar.bz2
mips64-linux.tar.bz2
mips-linux.tar.bz2
powerpc64-linux.tar.bz2
powerpc-linux.tar.bz2
s390-linux.tar.bz2
sh3-linux.tar.bz2
sh64-linux.tar.bz2
sparc64-linux.tar.bz2
sparc-linux.tar.bz2
v850e-linux.tar.bz2
vax-linux.tar.bz2
x86_64-linux.tar.bz2
xtensa-linux.tar.bz2
They seem to build reliably, I'd easily build them once a day. If
anybody is interested, I'll put them somewhere on lug-owl.de, or if
you wish, on kernel.org .
Comments?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
Signature of: GDB has a 'break' feature; why doesn't it have 'fix' too?
the second :
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-10 10:12 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 ` cross-compilers Tony Breeds
2009-04-09 23:47 ` cross-compilers Jan-Benedict Glaw
2009-04-10 10:12 ` Jan-Benedict Glaw [this message]
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=20090410101220.GF7921@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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 \
--cc=sam@ravnborg.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).