mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Cross Compiling [update]
Date: Sun, 22 Feb 2004 16:22:33 +0100	[thread overview]
Message-ID: <20040222152232.GB23051@MAIL.13thfloor.at> (raw)
In-Reply-To: <20040222124541.GA1064@gallifrey>

On Sun, Feb 22, 2004 at 12:45:41PM +0000, Dr. David Alan Gilbert wrote:
> * Herbert Poetzl (herbert@13thfloor.at) wrote:
> > 
> > Hi Folks!
> > 
> > Here is an update to the Kernel Cross Compiling thread 
> > I started ten days ago ...
> 
> Hi,
>    Quite a while ago I tried going through a similar
> process.   I found at the time the debian toolchain-source
> package helped in this process.
> 
> There is however one thing you seem to have missed - you
> tend to need subtely different versions of gcc and binutils
> for each combination.

not missed, but ignored on purpose ;)

> It certainly used to be the case that every architectures
> kernel used to have different known issues in both gcc
> and binutils; and there was a fair amount of 'oh don't
> use that version, it produces broken kernels' with
> different answers for each architecture.

hmm, that sounds too familiar, and I already prepared
to have different binutils, different gcc and some special
conditions for each build ... but I'm trying to minimize
the differences where possible ...

> At one time I tried to make a summary page showing where
> the kernel source and tools are for each architecture;
> but I never kept it upto date.
> (http://www.treblig.org/Linux_kernel_source_finder.html)

this looks quite useful, maybe you have some 'updated'
info, which could be of value to this efford, if so,
please let me know ...

anyway, thanks for the url, I was planning to do something
similar when I have all the details ...

best,
Herbert

> Dave
> 
>  -----Open up your eyes, open up your mind, open up your code -------   
> / Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
> \ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
>  \ _________________________|_____ http://www.treblig.org   |_______/
> -
> 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-22 15:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22  3:53 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 [this message]
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
2004-02-24  1:49     ` Dan Kegel
2004-02-24  8:53       ` Herbert Poetzl
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=20040222152232.GB23051@MAIL.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=gilbertd@treblig.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

all inboxes | Powered by JetHome®