public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Robert Schwebel <robert@schwebel.de>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Cross Compiling
Date: Sun, 15 Feb 2004 15:59:27 -0800	[thread overview]
Message-ID: <20040215235927.GC631@holomorphy.com> (raw)
In-Reply-To: <20040215232810.GK549@pengutronix.de>

On Sat, Feb 14, 2004 at 03:21:57PM +0100, Herbert Poetzl wrote:
>> thanks for the info, I read/tested that one too, some time
>> ago, but decided against this approach, as it builds the
>> glibc, which I do not need for the kernel toolchain at all
>> and I didn't want to bother with another source that won't
>> compile on arch xy ... maybe the wrong decision? I don't 
>> know ...

On Mon, Feb 16, 2004 at 12:28:11AM +0100, Robert Schwebel wrote:
> you might also want to have a look at the idea behind PTXdist (see
> http://www.pengutronix.de/software/ptxdist_en.html) which is also able
> to build toolchains and do all the necessary tweaking, without building
> a glibc (just only run 'make xchain-gccstage1' to get a compiler without
> glibc). It follows the same approach for the patch repositories like Dan
> and we are syncing heavily.
> The whole toolchain building is a huge mess at the moment.  

(a) The idiot thing was screwed wrt. binutils when the things were
	prefixed with e.g. sparc64-linux-gnu-$PROG; I managed to decipher
	where the paths were and just patch in the names of the crossutils.
(b) The stuff produced broken kernels; I had to resort to native builds
	anyway (which far from ideal, since it target violates host/target
	separation), and lost money getting a second of its kind to repair
	that state of affairs.

-- wli

  reply	other threads:[~2004-02-15 23:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-14  3:26 Kernel Cross Compiling 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 [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 21:03 Dan Kegel
2004-02-14 22:07 ` Herbert Poetzl
2004-02-15  3:51   ` Dan Kegel
     [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=20040215235927.GC631@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert@schwebel.de \
    /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