SBCL uses the "threads" USE flag. This is the same flag which is used for libperl (and perhaps also perl), and it is potentially dangerous there. I would suggest that a different flag be used for SBCL, as in my case I do care a lot about threads in SBCL, but I definitely do NOT want to destabilize anything by using it elsewhere. At the moment, I just take care to enable the flag when building SBCL and disabling it afterwards, but this is clearly suboptimal. Reproducible: Always Steps to Reproduce:
Agreed. The problem is the local USE flag system seems to lack a namespace. Until something like USE='-dev-lisp/sbcl:threads ...' is possible, we will rename the local use flag to 'sbcl-threads'
It is possible to specify specific USE sets on an per port basis. If you want threads for dev-lisp/sbcl and no threads for dev-lang/perl you should create /etc/portage/package.use to look like this: dev-lisp/sbcl threads dev-perl/perl -threads I can't find where this is documentented in the official documentation, however here are some references: http://bugs.gentoo.org/show_bug.cgi?id=13616 http://re.a.la/gentoo/flagguide/index.html.en http://gentoo-wiki.com/HOWTO_Use_Portage_Correctly It was news to me as well.
Good enough for me! I still believe the USE flags need to be reengineered -- sooner or later. But this solves my immediate problem for now.
