| Summary: | bootstrap: fails to emerge python 3.5.1 due to timeout | ||
|---|---|---|---|
| Product: | Gentoo/Alt | Reporter: | Jeffrey Ratcliffe <Jeffrey.Ratcliffe> |
| Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | blocker | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log | ||
|
Description
Jeffrey Ratcliffe
2016-02-03 13:02:21 UTC
Created attachment 424536 [details]
build.log
I have the same problem with dev-lang/python-3.4.3-r5, but not anything else in system. What OS are you bootstrapping on? Host OS is x86_64-with-redhat-5.6 And strangely, earlier on in the bootstrap process, both python 3.5.1 and 3.4.3 emerged OK. I think you're replacing your python when this happens. We might have to disable ipc during bootstrap or something. We disable ipc on anything non-linux, that explains why it doesn't manifest itself there. If I try and unset the ipc use flag in package.use, it is ignored. Can I do this without hacking the ebuild? If not, why have a flag? What do you mean with ignored? can you add -ipc to USE in the bootstrap script? Maybe it's use.forced, in which case we'll have to use the force a bit more to make sure it's not enabled during bootstapping. Does this still happen with newer Python? Python 3.5 is no longer in the main tree. No. This can be closed. |