From: Alexandre Oliva <aoliva@redhat.com>
To: "Marco" <gottini@bsecure.it>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: Built GCC 3.0! now installing it, ok! but i don't see it....
Date: Fri, 13 Jul 2001 12:40:00 -0000 [thread overview]
Message-ID: <org0c0obwr.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <005601c10b73$2a950b80$0200000a@ispettore>
On Jul 13, 2001, "Marco" <gottini@bsecure.it> wrote:
> Yes. i have it in /usr/local/bin. if i start it with full path it works!!!
Then you have to modify the PATH variable in your environment to get
/usr/local/bin/gcc found before /usr/bin/gcc
> now, may i uninstall the old one? (in /usr/bin)
It's not always a good idea.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
prev parent reply other threads:[~2001-07-13 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 5:37 Marco
2001-07-12 13:58 ` Alexandre Oliva
2001-07-13 1:09 ` Marco
2001-07-13 12:40 ` Alexandre Oliva [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=org0c0obwr.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gottini@bsecure.it \
/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).