On 26 May 2009, at 05:37, Volker Armin Hemmann wrote:
...
If a package would build using say 3dnow without the cpu supporting
it it will
crash with an instruction error. So either it works always or never.
Hmmmn.... so if I use it my applications might crash, but it's safe to
use?
The mplayer ebuild is stated to be "intelligent" about ignoring these
flags if necessary, so I'm not sure that "if mplayer works, so will
everything else" is a safe conclusion. My question was exactly if it
was so - are other ebuilds also as "intelligent" as mplayer?
Just look at /proc/cpuinfo you find everything you need to know
there. It
isn't hard. In fact, it is really ,really simple.
I'd disagree. If it were really simple, Portage would take care of it
automagically for me. It (apparently?) doesn't.
It's kinda a pain to have to look up what's supported on each system,
and then edit make.conf accordingly. Especially as some translation is
required: Adam Carter states, 'apparently "pni" = sse3'. What else
might be this or that or something else? The suggested `grep flags /
proc/cpuinfo` shows "apic sep mtrr" amongst others, but there appears
no USE flags corresponding to those. Or are there?
To keep my life simple, I'm going to use the absolute minimum of
flashypants hardware USE flags unless I know its safe.
Looks like `echo media-video/mplayer mmx mmxext sse sse2 ssse3 3dnow
3dnowext >> /etc/portage/package.use` unless someone else is able to
be more informative.
Stroller.
