| 1 |
On Friday 10 February 2006 01:26, Alec Warner wrote: |
| 2 |
> Assuming the CHOST variable is 'safe' is not a good thing, users can |
| 3 |
> over-ride this variable. Can you specify some behavior when it's set to |
| 4 |
> something bogus ( invalid form ) or something thats not in the mapping? |
| 5 |
Changing CHOST variable in something invalid for the current system is likely |
| 6 |
to kill everything that depends on CHOST and that currently means most of |
| 7 |
toolchain-funcs eclass, all the stuff depending on autotools (just a few |
| 8 |
packages, eh?) and every CHOST-based check. |
| 9 |
|
| 10 |
Users can change CHOST, but if they do in the wrong way, they can do way more |
| 11 |
damage than just this. |
| 12 |
|
| 13 |
-- |
| 14 |
Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/ |
| 15 |
Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE |
Archives