From: djfm <djfm@wanadoo.fr>
To: gcc@gcc.gnu.org
Subject: Changing gcc
Date: Tue, 01 Apr 2003 06:59:00 -0000 [thread overview]
Message-ID: <1049180154.14304.11.camel@pandemonium> (raw)
Hi!
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.
I have prefixes before app and folder names , such as
"i686-pc-linux-gnu-gcc" ...
I dunno what to do , what file to rename nor where to put them.
Please answer *simply* , Im absolutly new to linux.
Dont forget to explain the stupid etaps that I'm sure I would fail in.
Thx a lot by advance to all.
PS: I dunno whether I'm wrinting to a newsgroup or to an email. I'm not
used to it , I apologize.
Anyway please answer by mail.
And sorry for my bad english.
Thx again.
next reply other threads:[~2003-04-01 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 6:59 djfm [this message]
2003-04-01 7:49 ` Fergus Henderson
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=1049180154.14304.11.camel@pandemonium \
--to=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).