From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext"
Date: Tue, 26 May 2009 07:15:33 +0100 [thread overview]
Message-ID: <D5B68C25-2893-428B-83C8-40C6C0E7B523@stellar.eclipse.co.uk> (raw)
In-Reply-To: <200905260710.08709.volkerarmin@googlemail.com>
On 26 May 2009, at 06:10, Volker Armin Hemmann wrote:
>> ...
>> 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?
>>
>> ...
>> I'd disagree. If it were really simple, Portage would take care of it
>> automagically for me. It (apparently?) doesn't.
>
> portage does not take care. mplayers build has a cpu feature
> autodection.
>
> Different stuff. Really.
Right, that was the question. Thank you for answering it. Sorry if I
was unclear.
>> 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.
>
> yeah, except that is bullshit
So? It doesn't matter. Uh, I mean - that's what you just told me.
> no pentium can do 3dnow.
I did think that. But with other instructions adopted by the other
manufacturer (eg. Intel adopted the amd64 architecture, I think?) it
seemed odd that a set of instructions would be ignored so long.
> Or was there a 3dnow flag in /proc/mtrr? No? Then
> don't even touch it. Same for ssse3. This has nothing to do with
> sse3. It is
> something completly different. And p4 never had this.
That's cool. I'll just keep minimal hardware USE flags in make.conf;
in /etc/portage/package.use I'll tell mplayer to USE everything
(including 3dnow) that it can.
Thanks,
Stroller.
next prev parent reply other threads:[~2009-05-26 6:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 4:27 [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext" Stroller
2009-05-26 4:37 ` Adam Carter
2009-05-26 4:59 ` Volker Armin Hemmann
2009-05-26 4:37 ` Volker Armin Hemmann
2009-05-26 5:00 ` Stroller
2009-05-26 5:10 ` Volker Armin Hemmann
2009-05-26 6:15 ` Stroller [this message]
2009-05-26 6:27 ` Volker Armin Hemmann
2009-05-26 8:34 ` Stroller
2009-05-26 14:31 ` Daniel Iliev
2009-05-26 21:07 ` Stroller
2009-05-27 0:47 ` Daniel Iliev
2009-05-27 8:14 ` Stroller
2009-05-27 10:00 ` Daniel Iliev
2009-05-27 12:14 ` Stroller
2009-05-27 19:57 ` Wyatt Epp
2009-05-27 20:04 ` Volker Armin Hemmann
2009-05-27 20:09 ` Alan McKinnon
2009-05-27 20:40 ` Wyatt Epp
2009-05-27 20:47 ` Volker Armin Hemmann
2009-05-27 21:04 ` Mike Edenfield
2009-05-27 21:12 ` Alan McKinnon
2009-05-27 23:00 ` Adam Carter
2009-05-27 20:08 ` Ward Poelmans
2009-05-27 21:04 ` Mike Edenfield
2009-05-27 21:23 ` Arttu V.
2009-05-28 10:17 ` Daniel Iliev
2009-05-28 19:13 ` Stroller
2009-05-28 20:08 ` Ward Poelmans
2009-05-28 20:19 ` Stroller
2009-05-28 20:27 ` Ward Poelmans
2009-05-28 20:38 ` Stroller
2009-05-29 5:30 ` Graham Murray
2009-05-29 6:36 ` Volker Armin Hemmann
2009-05-29 6:55 ` Volker Armin Hemmann
2009-05-29 15:25 ` Mike Edenfield
2009-05-29 7:51 ` Neil Bothwick
2009-05-26 22:20 ` KH
2009-05-26 22:26 ` KH
2009-05-26 22:32 ` Alan McKinnon
2009-05-26 13:26 ` [gentoo-user] " James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D5B68C25-2893-428B-83C8-40C6C0E7B523@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox