From: Andrew Morton <akpm@linux-foundation.org>
To: Alex Chiang <achiang@hp.com>
Cc: Robin Holt <holt@sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org
Subject: Re: cross-compilers
Date: Tue, 7 Apr 2009 22:54:57 -0700 [thread overview]
Message-ID: <20090407225457.86f8a458.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090408054612.GA6744@ldl.fc.hp.com>
On Tue, 7 Apr 2009 23:46:12 -0600 Alex Chiang <achiang@hp.com> wrote:
> * Robin Holt <holt@sgi.com>:
> > Don't know if this answers your problem, but I use the tools from
> > emdebian and they do not suffer from the problems you list below.
>
> Wow, this seems _much_ simpler. Once you get the toolchain
> installed, all you have to do is set ARCH and CROSS_COMPILE
> appropriately?
>
> I guess the question remains for Andrew. Since I pretty much did
> all the work needed to update his cross-compiler repo, is there
> still value in it?
We would benefit very much from having someone who actually maintains a
suite of cross-compilers for kernel developers.
Yes, the stuff I put together is very old and at the time crosstool was
horridly hard to use. Hardly any combinations of anything actually
worked - what you see there is about 5% of the toolchains I had to
build. Apparently is has become better.
> Or shall we just recommend emdebian to everyone? :)
That sounds suspiciously like "thou shalt use debian". I was so
traumatised by dselect ten years ago that I don't think I could afford
the therapy bills.
next prev parent reply other threads:[~2009-04-08 5:57 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 ` Andrew Morton [this message]
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 ` 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=20090407225457.86f8a458.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=achiang@hp.com \
--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