From: Dan Kegel <dank@kegel.com>
To: Herbert Poetzl <herbert@13thfloor.at>, linux-kernel@vger.kernel.org
Subject: re: Kernel Cross Compiling
Date: Sat, 14 Feb 2004 13:03:22 -0800 [thread overview]
Message-ID: <402E8D1A.4000106@kegel.com> (raw)
Herbert Poetzl <herbert@13thfloor.at> wrote:
> I'm currently investigating the requirements/doability
> of a kernel cross compiling test bed/setup, able to do
> automated kernel builds for different architecture,
> just to see if it compiles and later to verify if a
> given patch breaks that compile on any of the tested
> archs ...
Great idea!
> I decided to use binutils 2.14.90.0.8, and gcc 3.3.2,
> but soon discovered that gcc-3.3.2 will not be able
> to build a cross compiler for some archs like the
> alpha, ia64, powerpc and even i386 ;) without some
> modifications[2] but with some help, I got all headers
> fixed, except for the ia64, which still doesn't work
Wouldn't it be easier to use http://kegel.com/crosstool
which already builds good toolchains for just about every
CPU type?
- Dan
--
US citizens: if you're considering voting for Bush, look at these first:
http://www.misleader.org/
http://www.cbc.ca/news/background/arar/
http://www.house.gov/reform/min/politicsandscience/
next reply other threads:[~2004-02-14 21:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 21:03 Dan Kegel [this message]
2004-02-14 22:07 ` Kernel Cross Compiling Herbert Poetzl
2004-02-15 3:51 ` Dan Kegel
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 21:51 Judith Lebzelter
2004-02-18 7:19 ` Herbert Poetzl
2004-02-14 3:26 Stephen M. Kenton
2004-02-14 14:21 ` Herbert Poetzl
2004-02-15 23:28 ` Robert Schwebel
2004-02-15 23:59 ` William Lee Irwin III
[not found] <20040213205743.GA30245@MAIL.13thfloor.at.suse.lists.linux.kernel>
2004-02-13 21:25 ` Andi Kleen
2004-02-13 21:46 ` Herbert Poetzl
2004-02-13 23:45 ` Herbert Poetzl
2004-02-15 11:16 ` Geert Uytterhoeven
2004-02-15 17:38 ` Herbert Poetzl
2004-02-16 13:51 ` Keith Owens
2004-02-13 20:57 Herbert Poetzl
2004-02-13 21:31 ` David Mosberger
2004-02-13 21:44 ` Herbert Poetzl
2004-02-14 0:58 ` David Mosberger
2004-02-14 1:08 ` Herbert Poetzl
2004-02-14 2:35 ` Herbert Poetzl
2004-02-14 2:51 ` David Mosberger
2004-02-16 22:50 ` Jim Wilson
2004-02-16 0:03 ` Peter Chubb
2004-02-14 8:32 ` Timothy D. Witham
2004-02-14 13:03 ` Herbert Poetzl
2004-02-14 19:25 ` Timothy D. Witham
2004-02-14 22:08 ` Herbert Poetzl
2004-02-16 21:41 ` cliff white
2004-02-16 22:10 ` Herbert Poetzl
2004-02-17 13:26 ` Maciej W. Rozycki
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=402E8D1A.4000106@kegel.com \
--to=dank@kegel.com \
--cc=herbert@13thfloor.at \
--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