From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext"
Date: Wed, 27 May 2009 22:09:36 +0200 [thread overview]
Message-ID: <200905272209.36348.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <200905272204.06302.volkerarmin@googlemail.com>
On Wednesday 27 May 2009 22:04:06 Volker Armin Hemmann wrote:
> On Mittwoch 27 Mai 2009, Wyatt Epp wrote:
> > On Wed, May 27, 2009 at 8:14 AM, Stroller
>
> <stroller@stellar.eclipse.co.uk>wrote:
> > > Of course, the amount of time I've spent on this thread, I could
> > > perhaps have learned *exactly* what all these extended instruction sets
> > > do, who designed them, whether they're cross-licensed between
> > > manufacturers and what their prospects are for continued support in the
> > > future. But I would personally find that very boring, and I am much
> > > happier to have learned a little about how mplayer's build system works
> > > and how Gentoo wraps that.
> >
> > It actually turns out that you can get the bare essentials on all of
> > these in about four minutes from Wikipedia. Just sayin'.... :)
> >
> > Reading this thread, though, it seems like it would be useful to have a
> > FEATURES=cpudetection for Portage. I honestly don't understand why the
> > user should have to be arsed to set those USEs manually if they don't
> > actually care about moving binary packages around. Thoughts?
>
> thoughts: there are distros that hold your hand already.
There's also Windows. For just in case Ubuntu doesn't hold enough of your
hand.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-05-27 20:11 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
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 [this message]
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=200905272209.36348.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--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