| 1 |
On Thu, 2008-12-11 at 08:02 +0100, Michael Haubenwallner wrote: |
| 2 |
> On Thu, 2008-12-11 at 01:00 +0000, Alan Hourihane wrote: |
| 3 |
> > Why do we reset EPREFIX in gcc-config - |
| 4 |
> |
| 5 |
> What is the problem with it? |
| 6 |
> |
| 7 |
> > isn't it already set by the |
| 8 |
> > SHELL ? |
| 9 |
> |
| 10 |
> Nope. |
| 11 |
> |
| 12 |
> Don't mix commandline-environment and ebuild-environment. |
| 13 |
> |
| 14 |
> There should be no need to have EPREFIX set in commandline-environment: |
| 15 |
> Simple Prefix binaries/scripts should work when they are called outside |
| 16 |
> prefix simply using /path/to/eprefix/usr/bin/somebinary. |
| 17 |
> |
| 18 |
> But portage does set it as part of the ebuild-environment, so the |
| 19 |
> ebuilds can encode into the built package for which EPREFIX it is built. |
| 20 |
|
| 21 |
Where does portage set it ? |
| 22 |
|
| 23 |
Alan. |
Archives