public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Cross Compiling
Date: Sat, 14 Feb 2004 19:51:00 -0800	[thread overview]
Message-ID: <402EECA4.4020703@kegel.com> (raw)
In-Reply-To: <20040214220726.GA13479@MAIL.13thfloor.at>

Herbert Poetzl wrote:
>>Wouldn't it be easier to use http://kegel.com/crosstool
>>which already builds good toolchains for just about every
>>CPU type?
> 
> 
> yeah Dan, I thought about that, and I guess I'll
> give that _another_ try soon, the reason I didn't
> choose that path, simply was, that I didn't want
> to compile the (g)libc, because I really do not 
> need it at all (kernel does not use/require that)
> and I didn't want to deal with that one too ...

Makes sense.  Simpler is better.

> btw, what archs did you verify? didn't find a 
> 'success' list or something like that, probably
> missed it somehow, anyway, currently I managed
> to compile binutils and gcc for:
> 
>  alpha, arm, cris, hppa/64, i386, ia64, m68k,
>  mips/64, ppc/64, s390, sh/4, sparc/64, v850,
>  x86_64 ...

I think I got most of those built except for hppa, ppc/64,
sparc/64, and v850.  (I've only run the gcc regression
tests on ppc405, ppc750, and sh4 so far, but hope to test more
later.)
Also, IBM seems to be using a variant of my script for ppc64.
- 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/

  reply	other threads:[~2004-02-15  3:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-14 21:03 Kernel Cross Compiling Dan Kegel
2004-02-14 22:07 ` Herbert Poetzl
2004-02-15  3:51   ` Dan Kegel [this message]
  -- 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=402EECA4.4020703@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