| Summary: | bootstrap fails due to python-2.7.6-r1 | ||
|---|---|---|---|
| Product: | Gentoo/Alt | Reporter: | iloveosxzfs |
| Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | bert, iloveosxzfs, vicegentoo |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | OS X | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
full build.log, compressed
emerge --info emerge -pqv ebuild environment Patch for Makefile.pre.in Patch for python-2.7.6-r1.ebuild |
||
|
Description
iloveosxzfs
2014-07-06 02:56:06 UTC
Created attachment 380278 [details]
full build.log, compressed
Created attachment 380280 [details]
emerge --info
Created attachment 380282 [details]
emerge -pqv
Created attachment 380284 [details]
ebuild environment
So while the "temporary workaround" worked at first and let python compile, the bootstrap fails again later with the same error, but this time with respect to 2.7.5-r4 while re-emerging python. I also just checked on my pre-existing prefix installation, and though python 2.7.6-r1 is installed successfully previously, it fails in the same place as the bootstrap if I try to re-emerge it. So this is a more general regression, not just one affecting bootstrap. I doubt this is the best way to fix the problem, but these patches together seemed to fix the problem: https://gist.githubusercontent.com/ilovezfs/25e20f0f4e33a8fddbf6/raw/6be8b39ce368937b132a8179d7acf66a1ba583c0/python-ebuild.patch https://gist.githubusercontent.com/ilovezfs/fd9a45fe62260a21760b/raw/bc6cb54f30e4cf796c8ffbf583af2a91e5157bd2/python-makefile-pre.patch Created attachment 380310 [details, diff]
Patch for Makefile.pre.in
Created attachment 380312 [details, diff]
Patch for python-2.7.6-r1.ebuild
Bug happens on my system too. This bug affects more than one user. Status should be set to confirmed. Same bug on my system. This bug affects more than one user. Status should be changed to confirmed. Hello ! I am new here so I am sorry, if something is missing. I downloaded the bootstrap script yesterday for the first time and had the same problem. This happened on Mac OS X 10.9.4 Mavericks with Xcode 5 and also on the same machine with 10.7.5 Lion with Xcode 4 and the old CLI tools. Please let me know, if you need more informations. Thanks for solving this bug. Another workaround I've found works is not to use the "aqua" USE flag with python-2.7.6-r1:
cd ${EPREFIX}
echo '=dev-lang/python-2.7.6-r1 -aqua' >> etc/portage/package.use
Thanks, that solved my problem ... but if you run the bootstrap-prefix.sh script the first time and it fails, then ${EPREFIX} is not set.
If
echo ${EPREFIX}
returns nothing, then the correct command is
echo '=dev-lang/python-2.7.6-r1 -aqua' >> $HOME/Gentoo/etc/portage/package.use
Or replace $HOME with the path you used as you run the script the first time.
Right. I did not mean to imply that your shell would magically know where you chose to put your Prefix installation. ;) It was not meaned bad from my side. I added the information only for people (like me) which are new to Gentoo-Prefix and had the same problem during the first run of the script. See the same thing on Lion Fix committed, I managed to get further in the bootstrap now. |