From: "Wichmann, Mats D" <mats.d.wichmann@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Back to the future: which gcc for kernel 2.4.18
Date: Fri, 14 Jun 2002 21:17:10 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905681@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905641@msgid-missing>
>>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 ?
>I'd suggest trying something like
> ftp://gcc.gnu.org/pub/gcc/releases/gcc-3.1/gcc-3.1.tar.bz2
>It shouldn't be too hard to build and install this.
In fact, if you just accept the default configure, the gcc built
from this tree will install into /usr/local and not step on
the existing gcc (but watch your paths). You're also pretty
much sure to end up needing a late-model binutils (the
current gnu release is 2.12.1, I believe) as gcc3 will,
depending on circumstances, emit some debugging stuff that the
linker can't handle if it's not recent enough.
prev parent reply other threads:[~2002-06-14 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 15:28 [Linux-ia64] Back to the future: which gcc for kernel 2.4.18 ? Xavier Bru
2002-06-05 17:34 ` David Mosberger
2002-06-13 23:40 ` Jim Wilson
2002-06-14 11:41 ` Xavier Bru
2002-06-14 17:04 ` Jim Wilson
2002-06-14 21:17 ` Wichmann, Mats D [this message]
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-105590701905681@msgid-missing \
--to=mats.d.wichmann@intel.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