This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author db3l
Recipients db3l, pablogsal, vstinner
Date 2019-04-25.21:17:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1556227077.5.0.0305158758669.issue36718@roundup.psfhosted.org>
In-reply-to
Content
Ok, I've resolved this, and the linker errors did actually point at the root issue.  They show trying to link extensions against /usr/local/lib/libpython2.7.a which was my test static build of 2.7.16.

Arguably this seems an issue in the buildbot build process in that it doesn't sandbox extension building to force linking to the python library being built rather than a random system library, but I can't see spending any time on that.  I've purged the 2.7.16 files from the /usr/local tree and things seem to be back to normal

I've started a new run for the failing build.
History
Date User Action Args
2019-04-25 21:17:57db3lsetrecipients: + db3l, vstinner, pablogsal
2019-04-25 21:17:57db3lsetmessageid: <1556227077.5.0.0305158758669.issue36718@roundup.psfhosted.org>
2019-04-25 21:17:57db3llinkissue36718 messages
2019-04-25 21:17:57db3lcreate