From: Dan Kegel <dank@kegel.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Peter Barada <peter@baradas.org>,
zack@codesourcery.com, pinskia@physics.uc.edu,
wilson@tuliptree.org, gcc@gcc.gnu.org, jbglaw@lug-owl.de
Subject: Re: cross-compilation documentation
Date: Mon, 23 Jun 2003 03:06:00 -0000 [thread overview]
Message-ID: <3EF610CF.2030506@kegel.com> (raw)
In-Reply-To: <20030622194204.GA7163@nevyn.them.org>
Jan-Benedict Glaw wrote:
>> That first step, installing bootstrap glibc headers, is a new
>> and annoying prerequisite as of gcc-3.3. See
>> http://sources.redhat.com/ml/crossgcc/2003-06/msg00170.html
>> for my rant on the subject.
>
> ACK.
>
> _But_ it's even worse that there's no[1] strict documentation on how to
> get a working cross-compiler. There are some "interesting"
> configurations which should have easily findable documentation.
> (Extensive --with-sysroot docs?).
>
> For me, toying mostly with around with Linux, my top wishlist is:
>
> - Building a Linux kernel-only cross compiler on my i386-linux
> box for some {mips|ppc|m68k|...}-linux target running
> efficiently on the box I build it on (BUILD == HOST).
> - Building a Linux kernel-only cross compiler on my i386-linux
> box for some {mips|ppc|m68k|...}-linux target running
> on any i386-like Linux machine (BUILD != HOST). So I can
> easily copy this binutils/compiler suite to some other box.
>
> - Building a full cross compiler (including userland and all
> sensefull languages) with BUILD == HOST as well as BULID !=
> HOST, but also keeping in mind that BUILD and HOST are nearly
> identical:)
OK, your wish is granted, I think. Even that last part.
See http://kegel.com/crosstool for my all-singing, all-dancing build script.
(I don't have m68k support yet, but since you asked, I'll try to add it today.)
> For all those who are trying to build cross compilers, you may find
> helpfull hints at my link list here:
> http://lug-owl.de/~jbglaw/linux-ports/#EasilyBuildableCrossToolchains
Very nice! I now link to that from http://www.kegel.com/crosstool/
- Dan
[ Please cc me, as I'm not subscribed to gcc. ]
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
next prev parent reply other threads:[~2003-06-22 20:15 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 0:36 Dan Kegel
2003-06-18 14:58 ` Joel Sherrill
2003-06-22 17:10 ` Dan Kegel
2003-06-19 0:00 ` Jim Wilson
2003-06-22 17:12 ` Dan Kegel
2003-06-22 17:19 ` Andrew Pinski
2003-06-22 17:21 ` Dan Kegel
2003-06-22 17:35 ` Peter Barada
2003-06-22 17:50 ` Andrew Pinski
2003-06-22 17:56 ` Jan-Benedict Glaw
2003-06-22 18:07 ` Zack Weinberg
2003-06-22 20:15 ` Dan Kegel
2003-06-22 20:27 ` Zack Weinberg
2003-06-22 20:36 ` Peter Barada
2003-06-22 21:10 ` Daniel Jacobowitz
2003-06-23 3:06 ` Dan Kegel [this message]
2003-06-23 4:08 ` Jan-Benedict Glaw
2003-06-23 4:22 ` Dan Kegel
2003-06-23 9:10 ` Peter Barada
2003-06-23 12:20 ` Dan Kegel
2003-06-23 12:15 ` Peter Barada
2003-06-23 12:20 ` Dan Kegel
2003-06-23 14:14 ` Peter Barada
2003-06-23 15:38 ` Hans-Peter Nilsson
2003-06-23 16:04 ` Dan Kegel
2003-06-23 16:11 ` Hans-Peter Nilsson
2003-06-23 15:57 ` Dan Kegel
2003-06-23 13:01 ` Daniel Jacobowitz
2003-06-23 14:14 ` Peter Barada
2003-06-23 14:50 ` Daniel Jacobowitz
2003-06-23 14:10 ` Daniel Jacobowitz
2003-06-22 18:41 ` Daniel Jacobowitz
2003-06-22 17:30 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2004-05-29 6:25 Dan Kegel
2004-05-29 6:57 ` Zack Weinberg
2004-06-01 16:35 ` Dan Kegel
2004-06-01 17:38 ` Dave Korn
2004-06-01 17:45 ` Peter Barada
2003-06-22 17:43 Dara Hazeghi
2003-06-22 17:49 ` Jan-Benedict Glaw
2003-06-22 17:49 ` Andrew Pinski
2003-06-22 17:53 ` Jan-Benedict Glaw
2003-06-24 5:26 ` Jim Wilson
2003-06-22 19:36 ` Dara Hazeghi
2003-06-27 12:13 ` Gerald Pfeifer
2001-11-13 16:21 Cross-compilation documentation Joseph S. Myers
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=3EF610CF.2030506@kegel.com \
--to=dank@kegel.com \
--cc=drow@mvista.com \
--cc=gcc@gcc.gnu.org \
--cc=jbglaw@lug-owl.de \
--cc=peter@baradas.org \
--cc=pinskia@physics.uc.edu \
--cc=wilson@tuliptree.org \
--cc=zack@codesourcery.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).