| 1 |
On Thu, 2008-12-11 at 01:00 +0000, Alan Hourihane wrote: |
| 2 |
> Why do we reset EPREFIX in gcc-config - |
| 3 |
|
| 4 |
What is the problem with it? |
| 5 |
|
| 6 |
> isn't it already set by the |
| 7 |
> SHELL ? |
| 8 |
|
| 9 |
Nope. |
| 10 |
|
| 11 |
Don't mix commandline-environment and ebuild-environment. |
| 12 |
|
| 13 |
There should be no need to have EPREFIX set in commandline-environment: |
| 14 |
Simple Prefix binaries/scripts should work when they are called outside |
| 15 |
prefix simply using /path/to/eprefix/usr/bin/somebinary. |
| 16 |
|
| 17 |
But portage does set it as part of the ebuild-environment, so the |
| 18 |
ebuilds can encode into the built package for which EPREFIX it is built. |
| 19 |
|
| 20 |
There are always too many environment variables around in |
| 21 |
commandline-environment. |
| 22 |
|
| 23 |
Although there is one exception for setting EPREFIX prior to an |
| 24 |
emerge-call in environment: cross-eprefix merge (don't want to explain |
| 25 |
the details here). |
| 26 |
|
| 27 |
/haubi/ |
| 28 |
-- |
| 29 |
Michael Haubenwallner |
| 30 |
Gentoo on a different level |
Archives