Message260258
I think the new regular expression will still find the wrong library in my libm example above. In 32-bit mode, it will be only looking to match \(libc6.*\). Since my example has the 64-bit line first, that one will match first. (I haven’t actually tested this, but I think I compiled 32-bit Python once before just by specifying CC="gcc -m32". Sorry to keep poking holes in your regular expression :)
Do you know if there is documentation for the “ldconfig -p” output format, or do we just have to go on what we see? If so, I would change it to ensure the ABI type string is either followed by a comma and space ", " or a closing bracket ")". A comma on its own, or other letters, is not a match.
I did a search for “find_library”, and the most likely place is /Lib/ctypes/test/test_find.py. You could probably get away with just adding a new method like Test_OpenGL_libs.test_path(). On my computer I have the GL and GLU libraries (but not gle), so I guess that these libraries are fairly common (plus it already has Windows and OS X versions to test). |
|
Date |
User |
Action |
Args |
2016-02-14 02:55:07 | martin.panter | set | recipients:
+ martin.panter, Hernan.Grecco, beng94 |
2016-02-14 02:55:06 | martin.panter | set | messageid: <1455418506.96.0.173067068481.issue21042@psf.upfronthosting.co.za> |
2016-02-14 02:55:06 | martin.panter | link | issue21042 messages |
2016-02-14 02:55:05 | martin.panter | create | |
|