1 |
On Wed, 27 May 2009 09:14:03 +0100 |
2 |
Stroller <stroller@××××××××××××××××××.uk> wrote: |
3 |
|
4 |
> |
5 |
> On 27 May 2009, at 01:47, Daniel Iliev wrote: |
6 |
> > |
7 |
> > There could be problems if you had enabled all the EIS flags |
8 |
> > globally (in make.conf) instead only for mplayer, because other |
9 |
> > programs don't have the "run-time cpu detection" feature and will |
10 |
> > fail in their attempts to use for example 3dnow! on an Intel CPU. |
11 |
> > |
12 |
> > I hope I was clear enough, apologies for my Englush. |
13 |
> |
14 |
> Hi there, |
15 |
> |
16 |
> The thing is that run-time CPU detection is unnecessary, if you're |
17 |
> always going to be using this mplayer binary you've just built on |
18 |
> the same system. mplayer will be built correctly without this |
19 |
> cpudetection flag (just put all the USE flags corresponding to EIS |
20 |
> instructions in package.use as previously discussed, but without |
21 |
> cpudetection). |
22 |
> |
23 |
|
24 |
I'm afraid the common sense says disabling the "cpudetection" USE |
25 |
flag could lead to the problem I described in my previous message. |
26 |
Please, don't get me wrong - I'm not arguing and I've never tried to |
27 |
build mplayer with EIS that is unsupported by the CPU. It may work if |
28 |
the build system detects and corrects such errors when cpudetection is |
29 |
disabled. |
30 |
|
31 |
I personally set the correct EIS USE flags for my CPU globally and |
32 |
disable the cpudetection flag. This has the advantage that all programs |
33 |
supporting one or another EIS would be built with the EIS code included. |
34 |
I didn't suggest you this approach because I believe somewhere in this |
35 |
thread you mentioned you wanted to use the same settings on several |
36 |
different systems. |
37 |
|
38 |
-- |
39 |
Best regards, |
40 |
Daniel |