after changing USE flags to include "nptl nptlonly", emerge -u glibc --newuse (sys-libs/glibc-2.3.4-20040808-r1) fails because it incorrectly depends on both linux-headers (virtual/os-headers) and linux26-headers, which is a block. Reproducible: Always Steps to Reproduce: 1. Add "nptl nptlonly" to Use 2. emerge -up --newuse glibc Actual Results: root@razorback / # emerge -up glibc --newuse These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] sys-kernel/linux-headers (from pkg sys-kernel/linux26-headers-2.6.8.1-r2) [ebuild N ] sys-kernel/linux-headers-2.4.21-r1 [ebuild N ] sys-kernel/linux26-headers-2.6.8.1-r2 [ebuild R ] sys-libs/glibc-2.3.4.20040808-r1 Expected Results: depended on only linux26-headers instead of both I plan to fix this ebuild asap.
I was screwing with this too, totally lost, after my reinstall right after Xmas mysteriously didnt have nptl... apparently i forgot the cflags. Then I came across this after some testing (I already had linux26-headers on, so i had to remove them to see what you're seeing). Here's the fix: Change your make.conf CHOST setting AWAY from i386 and it will work just fine. So then do a emerge glibc binutils gcc portage && emerge -e system and you should be OK.... You can do an emerge -e world if you would like, but let the updates take care of that on the next way thru your compiler. -Mark
closing, this isn't a bug.
