| 1 |
On Thursday 06 July 2006 13:00, Stuart Herbert wrote: |
| 2 |
> The one advantage of using USE flags for this is that the support can |
| 3 |
> be controlled very easily on a per-package basis. CFLAGS is much more |
| 4 |
> of a system-wide setting. |
| 5 |
There is always the bashrc to set CFLAGS on a per-package basis. |
| 6 |
|
| 7 |
> Are there examples where we'd want to have these CPU feature flags |
| 8 |
> enabled for one package, but disabled for another (for performance or |
| 9 |
> stability reasons)? |
| 10 |
I think the main issue would be with hardened, where mmx is already a problem |
| 11 |
on some packages, but I think this can be solved. |
| 12 |
For any package where enabling mmx create stability problem, it's likely the |
| 13 |
support should be removed altogether anyway, as the flag is enabled for the |
| 14 |
majority of users already (the same goes for the other flags). |
| 15 |
|
| 16 |
-- |
| 17 |
Diego "Flameeyes" Pettenò - http://farragut.flameeyes.is-a-geek.org/ |
| 18 |
Gentoo/Alt lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE |
Archives