From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: coexisting GCC versions
Date: Mon, 29 Jun 2009 03:18:54 +0200 [thread overview]
Message-ID: <200906290318.55482.wonko@wonkology.org> (raw)
In-Reply-To: <y65zlbsxdsx.fsf@minnie.esd.mun.ca>
Roger Mason writes:
> Now gcc-config says:
>
> garnet ~ $ gcc-config -l
> [1] i686-pc-linux-gnu-4.1.1
> [2] i686-pc-linux-gnu-4.3.2 *
>
> Whereas gcc -v says:
>
> <snip>
> gcc version 4.1.1 (Gentoo 4.1.1-r3 p1.10)
>
> If there is something else that I need to do then I did not see it in
> the upgrade guide, so please, will someone enlighten me?
No, your steps worked fine for me.
What is your $PATH? (echo $PATH)
I have /usr/i486-pc-linux-gnu/gcc-bin/4.1.2 in there (just before /usr/i686-
pc-linux-gnu/gcc-bin/4.3.2), don't know where this comes from. The directory
usr/i486-pc-linux-gnu/gcc-bin does not exist, so it does not matter.
Also have a look in /etc/env.d/*gcc*, do these settings look okay? That's
where gcc-config changes things. My 05gcc-i686-pc-linux-gnu has the line
PATH="/usr/i686-pc-linux-gnu/gcc-bin/4.3.2" in it.
Wonko
next prev parent reply other threads:[~2009-06-29 1:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 22:47 [gentoo-user] coexisting GCC versions Roger Mason
2009-06-27 23:14 ` Volker Armin Hemmann
2009-06-27 23:24 ` Alex Schuster
2009-06-27 23:31 ` Volker Armin Hemmann
2009-06-28 3:01 ` Dale
2009-06-28 3:37 ` Volker Armin Hemmann
2009-06-28 4:14 ` Dale
2009-06-28 3:39 ` Alex Schuster
2009-06-28 3:47 ` Volker Armin Hemmann
2009-06-28 8:26 ` Alan McKinnon
2009-06-28 8:41 ` Volker Armin Hemmann
2009-06-28 7:31 ` Dirk Heinrichs
2009-06-28 9:54 ` Roger Mason
2009-06-28 17:54 ` Roger Mason
2009-06-28 18:42 ` [gentoo-user] " Nikos Chantziaras
2009-06-28 21:13 ` Roger Mason
2009-06-29 1:18 ` Alex Schuster [this message]
2009-06-29 7:47 ` Roger Mason
2009-06-29 13:39 ` Alex Schuster
2009-06-30 8:50 ` [gentoo-user] Re: coexisting GCC versions [solved] Roger Mason
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=200906290318.55482.wonko@wonkology.org \
--to=wonko@wonkology.org \
--cc=gentoo-user@lists.gentoo.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