From: Bill Nottingham <notting@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: Back to the future: which gcc for kernel 2.4.18 ?
Date: Fri, 14 Jun 2002 18:25:50 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905679@msgid-missing> (raw)
Xavier Bru (Xavier.Bru@bull.net) said:
> Is there a clean way to do that for an unexperimented gcc user, in
> particular, can we have a gcc3.1 like installation that allows keeping
> the gcc2.96 ?
You should be able to rebuild:
ftp://people.redhat.com/jakub/gcc3/3.1-1/gcc3-3.1-1.src.rpm
and get something that installs alongside the 2.96 system compiler.
Bill
next reply other threads:[~2002-06-14 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 18:25 Bill Nottingham [this message]
2002-06-14 18:46 ` [Linux-ia64] Re: Back to the future: which gcc for kernel 2.4.18 ? David Mosberger
2002-06-17 16:12 ` Xavier Bru
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=marc-linux-ia64-105590701905679@msgid-missing \
--to=notting@redhat.com \
--cc=linux-ia64@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