After installing the binary linux download (STAF347-linux.tar.gz ), PYSTAF.so has unresolved symbols. I believe this is due to an incorrect path in makefile.linux.
When I run "ldd -r PYSTAF.so", I see the following output. The python library is not listed anywhere:
undefined symbol: Py_BuildValue (./PYSTAF.so)
undefined symbol: PyEval_RestoreThread (./PYSTAF.so)
undefined symbol: Py_InitModule4 (./PYSTAF.so)
undefined symbol: PyEval_SaveThread (./PYSTAF.so)
undefined symbol: PyArg_ParseTuple (./PYSTAF.so)
undefined symbol: PyErr_NewException (./PYSTAF.so)
linux-gate.so.1 => (0x0067a000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00bdc000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x004e9000)
libdl.so.2 => /lib/libdl.so.2 (0x002fa000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00da5000)
libm.so.6 => /lib/libm.so.6 (0x00b7b000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00a19000)
libc.so.6 => /lib/libc.so.6 (0x00110000)
When I build STAF from source, I do not have the same issue if I remove the trailing "config" from the PYTHON_V27_LIBDIRS path in makefile.linux.
After building from source, the output includes the following additional line and no undefined symbols:
libpython2.7.so.1.0 => /usr/lib/libpython2.7.so.1.0 (0xf7cdf000)
This issue prevents some of our tools from working with PySTAF and we currently have to build STAF from source to get around this issue.