I was just upgrading my bind installation, and as I don't have linux-caps, I have disabled the threads USE-flag (as described in several other bugs). But bind still compiles with linux-caps enabled. My guess is that it compiles per default _with_ linux-caps, and it did for me, because the ebuild only ENABLES linux-caps, but doesn't DISABLE them, if threads is disabled. Reproducible: Always Steps to Reproduce: 1. USE="-threads" emerge bind 2. try to run bind on a system without linux-caps 3. Actual Results: bind fails to start Expected Results: bind should start I made a binary package for bind, on a system which does have linux-caps. Dunno if that matters...
I made some changes to the ebuild and now it works! :-) Here is what I did: ---------------------------------- --- bind-9.2.5-r6.ebuild 2005-09-21 15:14:08.500140340 +0200 +++ bind-9.2.5-r6.ebuild_new 2005-09-21 15:13:27.950120946 +0200 @@ -107,6 +107,9 @@ src_compile() { myconf="${myconf} --enable-linux-caps --enable-threads" einfo "Threading support enabled" fi + else + myconf="${myconf} --disable-threads --disable-linux-caps" + einfo "Threading and Caps support disabled" fi econf \ ---------------------------------- I just disabled threads+caps if the threads USE-flag is disabled
Created attachment 68932 [details, diff] Proposed patch
*** Bug 107897 has been marked as a duplicate of this bug. ***
fixed in 9.2.5-r10, 9.3.1-r8 and 9.3.2_beta2-r2. thanks for reporting, Georges.