From: Peter Barada <peter@baradas.org>
To: dank@kegel.com
Cc: linux-kernel@vger.kernel.org, crossgcc@sources.redhat.com
Subject: Re: gcc-2.95 broken on PPC?
Date: Sat, 12 Apr 2003 15:12:22 -0400 (EDT) [thread overview]
Message-ID: <20030412191222.9654A98990@baradas.org> (raw)
In-Reply-To: <3E983288.9000000@kegel.com> (message from Dan Kegel on Sat, 12 Apr 2003 08:36:40 -0700)
> > The down side is that creating cross compilers from gcc 3.x is a lot
> > harder unless you already have a cross compiled glibc from gcc 2.95.x
> > in the proper paths.
>
>Yep. I'm not looking forward to dealing with that. Shame the gcc
>team keeps making building cross compilers harder.
It isn't that hard to build a cross compiler straight from the 3.x
sources; just takes an extra pass. I've had pretty good luck building
m68k-linux and ppc-linux cross C/C++ compilers from the sources, all I
needed to do was to build a boostrap C compiler that is used to build
glibc, and then come back and build a full up C/C++ compiler. Check
out the build script from Bill Gatliff's site:
<http://crossgcc.billgatliff.com/build-crossgcc.sh>
--
Peter Barada
peter@baradas.org
next prev parent reply other threads:[~2003-04-12 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 15:36 Dan Kegel
2003-04-12 19:12 ` Peter Barada [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-11 15:01 mikpe
2003-04-10 17:52 Dan Kegel
2003-04-10 17:50 ` Daniel Jacobowitz
2003-04-10 21:20 ` Wolfgang Denk
2003-04-10 21:32 ` Jörn Engel
2003-04-10 12:56 mikpe
2003-04-10 14:20 ` Benjamin Herrenschmidt
2003-04-10 14:42 ` Wolfgang Denk
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=20030412191222.9654A98990@baradas.org \
--to=peter@baradas.org \
--cc=crossgcc@sources.redhat.com \
--cc=dank@kegel.com \
--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®