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 15:39:22 +0200 [thread overview]
Message-ID: <200906291539.22318.wonko@wonkology.org> (raw)
In-Reply-To: <y65r5x3xz0l.fsf@minnie.esd.mun.ca>
Roger Mason writes:
> Alex Schuster <wonko@wonkology.org> writes:
> > 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.
Seems to be some leftover from the installation. I just deleted the
directory, and /etc/env.d/05gcc-i486-pc-linux-gnu.
> > 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.
>
> garnet ~ $ echo $PATH
> /home/rmason/.nix-profile/bin:/usr/local/coda/bin:/usr/local/coda/sbin:/u
>sr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/
>usr/i686-pc-linux-gnu/gcc-bin/4.3.2:/opt/sun-jdk-1.4.2.17/bin:/opt/sun-jdk
>-1.4.2.17/jre/bin:/opt/sun-jdk-1.4.2.17/jre/javaws:/usr/qt/3/bin:/home/rma
>son/bin:/usr/local/axiom/mnt/linux/bin:/usr/local/apache-uima//bin:/usr/lo
>cal/tau/i386_linux/bin:/usr/local/pdt/i386_linux/bin
[...]
> garnet ~ $ cat /etc/env.d/05gcc-i686-pc-linux-gnu
[...]
> PATH="/usr/i686-pc-linux-gnu/gcc-bin/4.3.2"
Looks good to me. Finally, what is the PATH in /etc/profile.env? According
to the order of your gcc paths, I guess it has /usr/i686-pc-linux-gnu/gcc-
bin/4.1.1:/usr/i686-pc-linux-gnu/gcc-bin/4.3.2 in it, while only the second
one should be there. Does "grep /usr/i686-pc-linux-gnu/gcc-bin/4.1.1
/ect/env.d/*" find something? Some obscure other file that env-update uses?
If not, I have no more ideas. I'd change /etc/profile.env by hand then, and
file a bug report.
Wonko
next prev parent reply other threads:[~2009-06-29 13:39 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
2009-06-29 7:47 ` Roger Mason
2009-06-29 13:39 ` Alex Schuster [this message]
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=200906291539.22318.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