public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Erik Van Reeth <erik@vanreeth.org>
To: Alan <alan@ufies.org>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Where is my GCC?
Date: Fri, 10 Jan 2003 01:14:26 +0100	[thread overview]
Message-ID: <200301100114.26752.erik@vanreeth.org> (raw)
In-Reply-To: <20030109233200.GA28588@ufies.org>

On Friday 10 January 2003 00:32, Alan wrote:
> Have you logged out and logged back in since it was rebuilt?  I Had the
> same thing this morning when gcc dissapeared from my path, and an
> env-update didn't fix, but just logged out and logged back in and all
> was well (*whew*)
>
> alan
>

The change came after the existance of 'gcc-config' program.
After running env-update, the ROOTPATH in /etc/profile is updated
to include /usr/i686-pc-linux-gnu/gcc-bin/3.2/gcc but the new
value is not activated yet.
This will done by doing a #source /etc/profile or by logout/login.

The env_update function in portage.py stipulates :
#parse /etc/env.d and generate /etc/profile.env

The env-update script does only a call to the function :
	import portage
	portage.env_update()

Better would be that the env-update script would re-read the /etc/profile.env
file. Bug ?

Greetz
Erik 

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-01-10  0:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 23:06 [gentoo-dev] Where is my GCC? Thomas T. Veldhouse
2003-01-09 23:15 ` Tony Clark
2003-01-09 23:22   ` Thomas T. Veldhouse
2003-01-09 23:32     ` Alan
2003-01-09 23:42       ` Thomas T. Veldhouse
2003-01-09 23:43         ` Arun Thomas
2003-01-10  1:02           ` Thomas T. Veldhouse
2003-01-10  0:03         ` Tony Clark
2003-01-10  0:05           ` Thomas T. Veldhouse
2003-01-10  0:14       ` Erik Van Reeth [this message]
2003-01-10  0:53         ` Thomas T. Veldhouse
2003-01-10 10:44 ` Spider

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=200301100114.26752.erik@vanreeth.org \
    --to=erik@vanreeth.org \
    --cc=alan@ufies.org \
    --cc=gentoo-dev@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