Michael Felt added the comment:
I have not looked specifically, at least not that I remember, for differences
in util/ctypes in python2 and python3. Will do so tomorrow.
I did just look briefly at the library, rather archive, built by default as
libpython2.7.a - it is static members only, i.e., my build using xlc (i.e., not
using gcc) does not build a shared object, so cdll.LoadLibrary and/or
find_library will not find anything for python2.7.. Neither will m, or libm, on
a default AIX system (with no other gcc based packages installed - these also
install a gnu rte where the utilities and libs you mention might include.
The few python packages I have found, packaged by others, tend to reload
everything yet again, not depending on anything that may already be there. And
to use shared libraries they are extracting the members from the .a archives
into two directories - when they support both 32 and 64-bit targets.
My intent is to examine the program to discover where libraries should be and
find the member name that is most likely. Also, if LIBPATH is defined, those
directories are searched first for a match.
In short, the key difference is to look at the program (probably python) for
the blibpath string in the application as well as python (from memory, sys.*
calls) to build a list of directories to search.
findLibrary('foo') first finds libfoo.a, then looks in libfoo.a for shr*.o
members, libfoo.so, libfoo.so.X and/or libfoo.so.X.Y, etc..
I need to check that findLibrary('foo.so') continues to work. At one time it
did, just have not looked at this for several weeks and I forget if it still
works. That is what I shall make sure stays in the "testing" part of the patch.
Michael
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26439>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
