Updating from python-2.7.12 to python-2.7.14, emerge fails with 'invalid install_name found' error. The relevant messages seem to be: * QA Notice: install_name references ${D}: /Users/anton/Gentoo/var/tmp/portage/dev-lang/python-2.7.14/image//Users/anton/Gentoo/usr/lib/Python.f ramework/Versions/2.7/Python in /Users/anton/Gentoo/usr/lib/Python.framework/Versions/2.7/bin/pythonw2.7 * QA Notice: install_name references ${D}: /Users/anton/Gentoo/var/tmp/portage/dev-lang/python-2.7.14/image//Users/anton/Gentoo/usr/lib/Python.f ramework/Versions/2.7/Python in /Users/anton/Gentoo/usr/lib/Python.framework/Versions/2.7/bin/python2.7 * QA Notice: invalid self-reference install_name /Users/anton/Gentoo/var/tmp/portage/dev-lang/python-2.7.14/image//Users/anton/Gentoo/usr/lib/Py thon.framework/Versions/2.7/Python in /Users/anton/Gentoo/usr/lib/Python.framework/Versions/2.7/Python * QA Notice: install_name references ${D}: /Users/anton/Gentoo/var/tmp/portage/dev-lang/python-2.7.14/image//Users/anton/Gentoo/usr/lib/Python.f ramework/Versions/2.7/Python in /Users/anton/Gentoo/usr/lib/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python I can re-emerge python-2.7.12 without problem, and I see no meaningful difference between the two ebuilds. Reproducible: Always
Created attachment 504146 [details] build.log
Created attachment 504148 [details] emerge --info '=dev-lang/python-2.7.14::gentoo_prefix'
Created attachment 504150 [details] emerge -pqv '=dev-lang/python-2.7.14::gentoo_prefix'
Created attachment 504248 [details] Accidentally working ebuild? Scratch "Reproducible: Always" Reproducible: Usually Trying to find the specific failure point, I re-run 'emerge -1 =dev-lang/python-2.7.14' several times; at one of the iterations emerge finished successfully. The only changes I was making was adding "einfo" statements to the ebuild (attached) The success looks intermittent: of the two subsequent attempts the first succeeded and the second failed.
Run into this problem at bootstraping. Adding FEATURES="${FEATURES} allow_broken_install_names" to etc/make.conf may bypass this for the present.
this is odd because it just installed fine on my Macs
python team has not much to do here, this is Prefix-specific.
(In reply to Fabian Groffen from comment #7) > python team has not much to do here, this is Prefix-specific. You are right, I have just blindly copied maintainers from the package metadata into the CC field. Sorry for that.
Hi Anton, my comment was directed at the python team, so they would know not to bother. You couldn't have known this, so no worries!
*** Bug 642260 has been marked as a duplicate of this bug. ***
Same problem here preventing bootstrap on High Sierra. Used allow_broken_install_names to get past this.
Anton's accidentally working ebuild only adds einfos, so I wonder if re-emerging python makes it work somehow. There is no real change between 2.7.12 and 2.7.14, but it very well may be a change in the python sources that causes this, but it definitely does work in some cases.
can you try and see if the fix for bug #642590 actually make this work better as well?
For the record, I got the same error with 10.13.3 on my Late 2013 MacBook Pro. Manually continued stage3 with: FEATURES="${FEATURES} allow_broken_install_names" ${EPREFIX}/bootstrap-prefix.sh ${EPREFIX} stage3_log but I got messages like: FEATURES variable contains unknown value(s): allow_broken_install_names so maybe that wasn't doing anything. But python-2.7.14 did install with no errors and stage3 completed.
I bootstrapped on High Sierra yesterday, and it succeeded without problems. Odd that it gives you this problem.
this problem should be long fixed by now, using Python 3.8.6 in bootstrap
