Most people have the order of flags to go /etc/portage/package.use then /etc/make.conf then /usr/portage/profiles. You can re-order it by adding a line to your /etc/make.conf... I remember reading it inepstevns40 wrote:I had glibc 4 fail during the configure stating that I needed to enable nptl and nptlonly use flags. These were clearly set in my make.conf, however, the the flags would not set on the emerge line. Doing a little digging in /usr/portage/profiles/default-linux/x86/2006.0/make.defaults the default make config line showed -nptl as the default. This was clobbering the /etc/make.conf USE flags and subsequently clobbering the glibc-2.4 ebuild.roderick wrote:So, since I tried (unsuccessfully) to install with nptlonly, should I build first the existing glibc 2.3.6-r3 with nptlonly and then try to upgrade to 2.4? Could that help?
I changed the -nptl to nptl in the default make profile and the glibc 2.4 ebuild compiled the way I have become accustomed- in other words-- very nicely
Should the "-nptl" in the 2006.0 profile be there for a reason or could this be a bug?
Hope this helps!
Code: Select all
man make.confIf you did not set this option then chances are you have forgotten a quotation mark on USE="", if you are using a text editor with word wrapping it might of broken line, etc. You can do aUSE_ORDER = "env:pkg:conf:auto:defaults"
Determines precedence for incrementing the setting of the USE vari-
able. The above setting will cause the environment (env) to over-
ride per package (pkg) settings to override make.conf (conf) to
override auto generated values from merged packages (auto) to over-
ride make.defaults (defaults).
***warning***
Do not modify this value unless you're a developer and you know
what you're doing. If you change this and something breaks, we will
not help you fix it.
Defaults to "env:pkg:conf:auto:defaults".
Code: Select all
emerge --info




