public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Chris Friesen <cfriesen@nortelnetworks.com>
Subject: re: any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc?
Date: Tue, 02 Apr 2002 11:43:28 -0800	[thread overview]
Message-ID: <3CAA09E0.6549FD7F@kegel.com> (raw)

Chris Friesen <cfriesen@nortelnetworks.com> wrote:
> We're looking at moving to gcc 3.x for 2.4.18, and are trying to decide what
> version to use.  It appears that there were some ppc-specific fixes that went in
> to 3.1, and I'm not sure if they were ported back to 3.0.
> 
> Has anyone had any successes or failures using either of these versions on ppc? 
> Any gotchas?

I'm about to do the same thing.  I'm already using a (patched) gcc3.0.2
on sh4, and really want to drop gcc2.9x for ppc, too.  Haven't tried
it yet, though.

Have you asked on linuxppc-{dev,user}@lists.linuxppc.org yet?
(Archives at http://lists.linuxppc.org/ )
- Dan

             reply	other threads:[~2002-04-02 19:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 19:43 Dan Kegel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-02 17:53 any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc? Chris Friesen

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=3CAA09E0.6549FD7F@kegel.com \
    --to=dank@kegel.com \
    --cc=cfriesen@nortelnetworks.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