From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc?
Date: Tue, 02 Apr 2002 15:06:37 -0500 [thread overview]
Message-ID: <3CAA0F4D.26C3A8BC@nortelnetworks.com> (raw)
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
2.4.18 on ppc?
Any gotchas?
Thanks,
Chris
PS. Please cc me on replies, as I'm not subscribed to the list at the moment.
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-04-02 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 20:06 Chris Friesen [this message]
2002-04-02 20:14 ` any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc? Franz Sirl
2002-04-02 20:30 ` Andrew Bradley
2002-04-02 20:22 ` Andrew Bradley
2002-04-02 20:33 ` Franz Sirl
2002-04-02 21:36 ` Andrew Bradley
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=3CAA0F4D.26C3A8BC@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linuxppc-dev@lists.linuxppc.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).