Section 6.c. Progressing from Stage1 to Stage2, code listing 14. It currently reads: # emerge -C linux-headers # emerge --oneshot linux26-headers # scripts/bootstrap.sh It should read: # emerge -C linux-headers # emerge --nodeps linux26-headers # scripts/bootstrap.sh When emerging linux26-headers with the --oneshot option, it attempts to emerge glibc first, which fails because it needs linux26-headers for nptl, and linux26-headers isn't installed yet. Catch-22. Using --nodeps instead installs the headers, and then the bootstrap can proceed. I think the confusion came about because the short option for --nodeps is -o. Reproducible: Always Steps to Reproduce:
*** Bug 73766 has been marked as a duplicate of this bug. ***
*** Bug 73998 has been marked as a duplicate of this bug. ***
Someone please tell me a way without "--nodeps". What will our users think when we tell them to use a flag that ignores dependencies...
integrate it into bootstrap.sh ? bootstrap.sh can check to see if USE=nptl and if so, clean out linux-headers and emerge linux26-headers if need be
Bleh, I've added in the --nodeps due to "popular demand", but I won't resolve this bug. I'd rather see a clean solution so we can remove the use of --nodeps again.
Bleh, enough discussion and stuff. Seems like it's the only solution currently until the new release.