public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: Jim Wilson <wilson@specifixinc.com>
Cc: linux-kernel@vger.kernel.org, Judith Lebzelter <judith@osdl.org>,
	Dan Kegel <dank@kegel.com>, cliff white <cliffw@osdl.org>,
	"Timothy D. Witham" <wookie@osdl.org>
Subject: Re: Kernel Cross Compiling [update]
Date: Mon, 23 Feb 2004 21:32:57 +0100	[thread overview]
Message-ID: <20040223203257.GA9800@MAIL.13thfloor.at> (raw)
In-Reply-To: <1077565352.1054.22.camel@leaf.tuliptree.org>

On Mon, Feb 23, 2004 at 11:42:31AM -0800, Jim Wilson wrote:
> On Sat, 2004-02-21 at 19:53, Herbert Poetzl wrote:
> > Here is an update to the Kernel Cross Compiling thread 
> > I started ten days ago ...
> 
> If you want gcc to be fixed so the inhibit_libc builds work for linux
> targets, then I suggest opening an FSF gcc bugzilla bug report.  Sending
> mail to me or to the linux kernel mailing list is unlikely to accomplish
> this.

hmm, sorry, I didn't want to tantalize you with mails,
I just thought you would be interested in them ...

my apologies here, will avoid further mails to your account

my primary goal isn't to get this fixed by the gcc folks,
I want to have a simple and working solution, which seems
to be at hand for the toolchains, to cross compile the
linux kernel for testing purposes. the changes so far are
not very intrusive IMHO, and I can live with a few patches.
(btw. currently Dan Kegel has a lot more patches to gcc in 
his toolchain than I do)

> FYI David Mosberger sent me a comment in private mail pointing out that
> if you are trying to bootstrap linux on a new target, then requiring a
> glibc port before the kernel port is a problem.  I consider this a good
> reason to make this feature work.

sounds reasonable ... at least to me ;)

> However, my recommendation still stands.  In general, I do not recommend
> building inhibit_libc crosses for linux targets, even though such
> crosses are likely to work fine for building a kernel.  As a gcc
> maintainer, it makes my job harder when people are building the compiler
> different ways, because I may get bug reports that I can't reproduce or
> understand.  Also, there is a risk that a kernel-only cross compiler
> will accidentally be used for some other purpose, resulting in a bug
> report that wastes the time of the gcc maintainers.

originally I had the weird? opinion, that gcc (or it's
build system) does support the cross target to exactly
do this (building an initial gcc, which can be used to
compile other stuff, like (g)libc and such) ...

that this looks like some kind of hack is neither my fault
nor does it justify messing around with 'unbuildable'
(g)libcs to get a kernel cross compile working ...

best,
Herbert

> -- 
> Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2004-02-23 20:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22  3:53 Kernel Cross Compiling [update] Herbert Poetzl
2004-02-22  6:02 ` Dan Kegel
2004-02-22 15:42   ` Herbert Poetzl
2004-02-22  8:43 ` Geert Uytterhoeven
2004-02-22  9:07 ` Russell King
2004-02-22 15:09   ` Herbert Poetzl
2004-02-22 12:45 ` Dr. David Alan Gilbert
2004-02-22 15:22   ` Herbert Poetzl
2004-02-22 15:52 ` Paul Mundt
2004-02-22 17:07   ` Herbert Poetzl
2004-02-22 17:23     ` Paul Mundt
2004-02-23 13:28       ` Richard Curnow
2004-02-23 14:41         ` Herbert Poetzl
2004-02-26 13:02           ` Richard Curnow
2004-02-23 19:42 ` Jim Wilson
2004-02-23 20:32   ` Herbert Poetzl [this message]
2004-02-24  1:49     ` Dan Kegel
2004-02-24  8:53       ` Herbert Poetzl
  -- strict thread matches above, loose matches on Subject: below --
2004-02-22 16:36 Arnd Bergmann

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=20040223203257.GA9800@MAIL.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=cliffw@osdl.org \
    --cc=dank@kegel.com \
    --cc=judith@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wilson@specifixinc.com \
    --cc=wookie@osdl.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