From: Fergus Henderson <fjh@cs.mu.oz.au>
To: djfm <djfm@wanadoo.fr>
Cc: gcc@gcc.gnu.org
Subject: Re: Changing gcc
Date: Tue, 01 Apr 2003 07:49:00 -0000 [thread overview]
Message-ID: <20030401074916.GA13035@earth.cs.mu.oz.au> (raw)
In-Reply-To: <1049180154.14304.11.camel@pandemonium>
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
On 01-Apr-2003, djfm <djfm@wanadoo.fr> wrote:
>
> I'm new to Linux , I am under mandrake 8.2 , and I wanted to upgrade my
> gcc native compiler (2.96) to the last 3.2.2 , I downloaded it on
> gcc.gnu.org , and followed the compilation instructions. Or I may
> suppose to have done so. I've made a "make bootstrap" , all seem to have
> worked correctly , now I have the binaries and libraries installed in
> usr/local/ but they have not self-replaced the old ones.
Leave the old files where they are, and just change your PATH
environment variable so that /usr/local/bin (or whereever you installed
the new gcc) is included at the start.
E.g. if you are using bash, you can add the following line to your
~/.bash_profile file:
PATH=/usr/local/bin:$PATH
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
The University of Melbourne | of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.
--------------------------------------------------------------------
This message could not be encrypted because no digital certificate
was found for your address. However, you can encrypt your reply with
the certificate attached below. Details at www.unicrypt.com.au
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3083 bytes --]
next prev parent reply other threads:[~2003-04-01 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 6:59 djfm
2003-04-01 7:49 ` Fergus Henderson [this message]
2008-01-05 18:07 changing gcc amnon stanislavsky
2008-01-05 20:57 ` Ian Lance Taylor
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=20030401074916.GA13035@earth.cs.mu.oz.au \
--to=fjh@cs.mu.oz.au \
--cc=djfm@wanadoo.fr \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).