Author martin.panter
Recipients Hernan.Grecco, beng94, berker.peksag, martin.panter, python-dev
Date 2016-03-09.03:20:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457493659.15.0.650449686479.issue21042@psf.upfronthosting.co.za>
In-reply-to
Content
It looks like the ldconfig parsing isn’t working for some ABIs. See the following buildbot failures:

* Cortex A15 armv7l: http://buildbot.python.org/all/builders/ARMv7%20Ubuntu%203.x/builds/3721/steps/test/logs/stdio
* ppc64le POWER8: http://buildbot.python.org/all/builders/PPC64LE%20Fedora%203.x/builds/769/steps/test/logs/stdio

I presume there are other flags in the ABI string, perhaps like (libc6,hard-float) on ARM. The code that produces these strings seems to be here: <https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=blob;f=elf/cache.c;h=fbee172#l72>.

Looking closer at the find_library() implementation, I also realize it is not correct to say an absolute path is always returned. If the ldconfig check fails, it falls back to _get_soname(). I think we have the following options:

* Adjust the documentation to say an absolute path is only returned if the ldconfig call works
* Figure out how to get the right ldconfig flags for ARM and PPC
* Use the old parsing code on ARM and PPC platforms, and only return a full path on x86 or other platforms
* Revert the whole change
History
Date User Action Args
2016-03-09 03:20:59martin.pantersetrecipients: + martin.panter, python-dev, berker.peksag, Hernan.Grecco, beng94
2016-03-09 03:20:59martin.pantersetmessageid: <1457493659.15.0.650449686479.issue21042@psf.upfronthosting.co.za>
2016-03-09 03:20:59martin.panterlinkissue21042 messages
2016-03-09 03:20:58martin.pantercreate