From: Dan Kegel <dank@kegel.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
crossgcc@sources.redhat.com
Subject: Re: gcc-2.95 broken on PPC?
Date: Sat, 12 Apr 2003 08:36:40 -0700 [thread overview]
Message-ID: <3E983288.9000000@kegel.com> (raw)
A high white horse souse wrote:
> I wouldn't switch to gcc-3.3 for now, the gcc mailing list looks like it
> has more problems and less features than the unstable bleeding edge
> gcc-3.4 CVS version. I am using gcc 3.2.2 for everything. I compiled
> my X, my libc, my kernel, my KDE. That is the first 3.x version that
> didn't produce incorrect code for any of these.
Thanks for the info. I feel a lot better about trying gcc-3.2.2 now.
Does anyone know if it needs patches to produce a working kernel
and glibc on sh4? gcc-3.0.4 needed a sizable patch on sh4, I seem to recall,
but not on ppc.
> 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.
- Dan
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
next reply other threads:[~2003-04-12 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 15:36 Dan Kegel [this message]
2003-04-12 19:12 ` gcc-2.95 broken on PPC? Peter Barada
-- 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=3E983288.9000000@kegel.com \
--to=dank@kegel.com \
--cc=crossgcc@sources.redhat.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;
as well as URLs for NNTP newsgroup(s).