| 1 |
On 7/6/06, Diego 'Flameeyes' Pettenò <flameeyes@g.o> wrote: |
| 2 |
> Right now we have mmx, 3dnow, 3dnowex, sse, sse2 and so on useflags present in |
| 3 |
> the tree, almost never used to get new dependencies, but usually used to |
| 4 |
> supply econf switches. |
| 5 |
|
| 6 |
Hoping the S/N ratio here hasn't gotten too high... |
| 7 |
|
| 8 |
IMO the main purpose of USE flags should be econf switches. Pulling |
| 9 |
in dependancies should be viewed as more of a side-effect, even if a |
| 10 |
common one. If the user wants "./configure ... --enable-gtk", then |
| 11 |
they need gtk on their box. |
| 12 |
|
| 13 |
Similarly, the mmx,sse,3dnow,etc useflags should be there for econf |
| 14 |
switches, not additions to CFLAGS. If the autoconf script has an |
| 15 |
--enable-mmx option, then the proper way to control that is through a |
| 16 |
useflag. |
| 17 |
|
| 18 |
I don't object to ebuilds adding CFLAGS/CXXFLAGS based on the result |
| 19 |
of your has_cpuset (for example, --fpmath= could be useful), but I |
| 20 |
don't believe has_cpuset should be used to set econf switches. |
| 21 |
|
| 22 |
And users should absolutely not have to muck with bashrc to disable |
| 23 |
this. Add a FEATURE, or something, to enable/disable it if necessary. |
| 24 |
|
| 25 |
-Richard |
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives