| 1 |
On Thu, 28 May 2009 00:23:52 +0300 |
| 2 |
"Arttu V." <arttuv69@×××××.com> wrote: |
| 3 |
|
| 4 |
> On 5/27/09, Wyatt Epp <wyatt.epp@×××××.com> wrote: |
| 5 |
> > Reading this thread, though, it seems like it would be useful to |
| 6 |
> > have a FEATURES=cpudetection for Portage. |
| 7 |
> |
| 8 |
> Congratulations, it's already there! Sort of. -march=native ;) |
| 9 |
> |
| 10 |
|
| 11 |
Not the same thing. "-march=" instructs gcc to produce a binary |
| 12 |
designed to run only on the given CPU architecture, while |
| 13 |
USE flags instruct the build system to include or not support for a |
| 14 |
given feature. Think of the USE flags "this" and "that" as shortcuts to |
| 15 |
"./configure --enable-this --disable-that". |
| 16 |
|
| 17 |
So, for example mplayer could be a binary which can take advantage (or |
| 18 |
not) of SSSE3 and is designed to run only (or not) on core2. |
| 19 |
|
| 20 |
|
| 21 |
P.S. |
| 22 |
|
| 23 |
And what's next - feature like: |
| 24 |
|
| 25 |
FEATURES="do_the_best_system_ever" |
| 26 |
|
| 27 |
where "do_the_best_system_ever" is a shorthand for: |
| 28 |
|
| 29 |
detect_best_cflags |
| 30 |
detect_best_cxxflags |
| 31 |
detect_best_ldflags |
| 32 |
detect_best_uselags |
| 33 |
|
| 34 |
Sounds good and it's not against Gentoo philosophy - the end user has |
| 35 |
the choice to use this feature or not. Any volunteers for the |
| 36 |
implementation? Oh, wait! Somebody define "best", please! :) |
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
Best regards, |
| 41 |
Daniel |
Archives