| 1 |
On Fri, Feb 11, 2011 at 1:56 PM, James <wireless@×××××××××××.com> wrote: |
| 2 |
> But, this has made me think. Is setting nptl and |
| 3 |
> nptl globally (in make.conf) the best idea? |
| 4 |
> |
| 5 |
> Should the threads flag also be set globally, or just |
| 6 |
> on a per package basis? Maybe nptl and threads |
| 7 |
> and not set nptlonly? |
| 8 |
> |
| 9 |
|
| 10 |
I have threads set globally in make.conf and haven't run into any |
| 11 |
issues. nptl and nptlonly are set via make.defaults in amd64 profile. |
| 12 |
|
| 13 |
It doesn't seem like too many of the packages I actually use have a |
| 14 |
"threads" use flag: |
| 15 |
|
| 16 |
floppym@naomi ~ % equery hasuse threads | cat |
| 17 |
app-arch/xz-utils-5.0.1 |
| 18 |
app-emulation/wine-1.3.13 |
| 19 |
dev-cpp/clucene-0.9.21b-r1 |
| 20 |
dev-cpp/libthrowable-1.1.0 |
| 21 |
dev-lang/python-2.6.6-r1 |
| 22 |
dev-lang/python-2.7.1 |
| 23 |
dev-lang/python-3.1.2-r4 |
| 24 |
dev-lang/ruby-1.8.7_p302 |
| 25 |
dev-lang/tcl-8.5.8-r1 |
| 26 |
dev-lang/tk-8.5.8-r1 |
| 27 |
dev-libs/beecrypt-4.1.2-r1 |
| 28 |
dev-vcs/git-1.7.3.4-r1 |
| 29 |
media-libs/libvpx-0.9.5 |
| 30 |
media-libs/x264-0.0.20101029 |
| 31 |
media-video/ffmpeg-0.6_p25767 |
| 32 |
net-analyzer/wireshark-1.4.3 |
| 33 |
net-dns/bind-9.7.2_p3-r3 |
| 34 |
net-print/cups-1.4.6 |
| 35 |
|
| 36 |
I'm sure many other packages use threads, but it isn't optional. |
Archives