| 1 |
On Wednesday 27 May 2009 00:20:50 KH wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> so I temporarily disable all USE flags in my make.conf by adding the "#" |
| 5 |
> to the line. Some with package.use. |
| 6 |
> The I run : |
| 7 |
> |
| 8 |
> USE="cpudetection" emerge -pv mplayer |
| 9 |
> |
| 10 |
> See output below. |
| 11 |
> |
| 12 |
> So what changes for me: oss is added. That's nothing for hardware and I |
| 13 |
> use alsa, so I don't need it, do I? |
| 14 |
> -aalib -cddb -cdparanoia -debug -dirac -dvb (not hardware) |
| 15 |
> -pvr (it's software too, isn't it?) |
| 16 |
> -samba -schroedinger -xinerama (not hardware) |
| 17 |
> |
| 18 |
> |
| 19 |
> Is this a valid way of approache? |
| 20 |
> |
| 21 |
> So My USE flags are set correct (for hardware) aren't they? |
| 22 |
|
| 23 |
No, you have it wrong. |
| 24 |
|
| 25 |
The ebuild does not magically change the USE flags based on what you have. It |
| 26 |
will build according to what you tell it, no more, no less. |
| 27 |
|
| 28 |
USE=cpudetection causes special code to be compiled into mplayer. Think of it |
| 29 |
this way (a highly simplistic explanation that gets the point across): |
| 30 |
|
| 31 |
mplayer is built with routines for every possible optimization. At RUNTIME, |
| 32 |
when mplayer starts, it figures out what you have and what you can use, and |
| 33 |
remembers for itself the routines you can't use and does not run them. |
| 34 |
|
| 35 |
cpudetection changes runtime behaviour, not compile time behaviour, and does |
| 36 |
not change your use flags at all. When you hashed out the line in |
| 37 |
/etc/make.conf, all you proved is that with the exception of oss, your |
| 38 |
configured USE flags for mplayer are the same as the default for your profile |
| 39 |
and mplayer. |
| 40 |
|
| 41 |
-- |
| 42 |
alan dot mckinnon at gmail dot com |
Archives