On Fri, Feb 11, 2011 at 1:56 PM, James <wirel...@tampabay.rr.com> wrote: > But, this has made me think. Is setting nptl and > nptl globally (in make.conf) the best idea? > > Should the threads flag also be set globally, or just > on a per package basis? Maybe nptl and threads > and not set nptlonly? >
I have threads set globally in make.conf and haven't run into any issues. nptl and nptlonly are set via make.defaults in amd64 profile. It doesn't seem like too many of the packages I actually use have a "threads" use flag: floppym@naomi ~ % equery hasuse threads | cat app-arch/xz-utils-5.0.1 app-emulation/wine-1.3.13 dev-cpp/clucene-0.9.21b-r1 dev-cpp/libthrowable-1.1.0 dev-lang/python-2.6.6-r1 dev-lang/python-2.7.1 dev-lang/python-3.1.2-r4 dev-lang/ruby-1.8.7_p302 dev-lang/tcl-8.5.8-r1 dev-lang/tk-8.5.8-r1 dev-libs/beecrypt-4.1.2-r1 dev-vcs/git-1.7.3.4-r1 media-libs/libvpx-0.9.5 media-libs/x264-0.0.20101029 media-video/ffmpeg-0.6_p25767 net-analyzer/wireshark-1.4.3 net-dns/bind-9.7.2_p3-r3 net-print/cups-1.4.6 I'm sure many other packages use threads, but it isn't optional.
