Here's also the entire build script out if that helps. Wasn't sure if it would be too long for the e-mail thread, so I tossed it on pastebin.
http://pastebin.com/7r6r6hed Are there any tips for debugging this? In regards to the libraries it links against, should there be one that points to something in particular? Are there any good tips for debugging this? On Wed, Jan 11, 2012 at 6:08 AM, Josh Stratton <strattonbra...@gmail.com> wrote: > $ ldd -r Sunshine.so > linux-vdso.so.1 => (0x00007fff297ff000) > libdl.so.2 => /lib64/libdl.so.2 (0x00007fdda756a000) > libutil.so.1 => /lib64/libutil.so.1 (0x00007fdda7367000) > libpython2.7.so.1.0 => /usr/lib64/libpython2.7.so.1.0 > (0x00007fdda6fa9000) > libGLEW.so.1.6 => /usr/lib64/libGLEW.so.1.6 (0x00007fdda6d3f000) > libboost_python.so.1.47.0 => /usr/lib64/libboost_python.so.1.47.0 > (0x00007fdda6aef000) > libQtScript.so.4 => /usr/lib64/libQtScript.so.4 (0x00007fdda664d000) > libQtOpenGL.so.4 => /usr/lib64/libQtOpenGL.so.4 (0x00007fdda6351000) > libQtGui.so.4 => /usr/lib64/libQtGui.so.4 (0x00007fdda5699000) > libQtCore.so.4 => /usr/lib64/libQtCore.so.4 (0x00007fdda51c9000) > libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x00007fdda4eb3000) > libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fdda4c97000) > libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fdda498f000) > libm.so.6 => /lib64/libm.so.6 (0x00007fdda470b000) > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fdda44f6000) > libc.so.6 => /lib64/libc.so.6 (0x00007fdda413f000) > /lib64/ld-linux-x86-64.so.2 (0x0000003037000000) > libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fdda3e01000) > libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x00007fdda3b94000) > libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007fdda38f4000) > libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007fdda36e4000) > libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007fdda34da000) > libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007fdda32d1000) > libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007fdda30cb000) > libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007fdda2ec1000) > libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007fdda2cbe000) > libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 > (0x00007fdda2a89000) > libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007fdda2876000) > libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007fdda2670000) > librt.so.1 => /lib64/librt.so.1 (0x00007fdda2468000) > libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007fdda2148000) > libpng12.so.0 => /usr/lib64/libpng12.so.0 (0x00007fdda1f20000) > libz.so.1 => /lib64/libz.so.1 (0x00007fdda1d09000) > libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007fdda1aba000) > libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007fdda18b2000) > libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007fdda1697000) > libnvidia-tls.so.290.10 => > /usr/lib64/nvidia/tls/libnvidia-tls.so.290.10 (0x00007fdda1493000) > libnvidia-glcore.so.290.10 => > /usr/lib64/nvidia/libnvidia-glcore.so.290.10 (0x00007fdd9f18c000) > libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fdd9ef70000) > libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fdd9ed47000) > libffi.so.5 => /usr/lib64/libffi.so.5 (0x00007fdd9eb3e000) > libuuid.so.1 => /lib64/libuuid.so.1 (0x00007fdd9e939000) > libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fdd9e736000) > > On Wed, Jan 11, 2012 at 4:27 AM, Hugo Parente Lima > <hugo.l...@openbossa.org> wrote: >> On Wednesday 11 January 2012 03:25:10 strattonbrazil wrote: >>> I've been trying to follow this to see if I can launch my qt app from >>> python using pyside. >>> >>> http://lynxline.com/superhybrids-part-2-now-qt-pyside/ >>> >>> I think I have the general idea of how everything works, but after >>> creation of my shared libraries, I can't import it in python without >>> getting an import error. >>> >>> libsunshine.so -> libsunshine.so.1.0.0 >>> libSunshine.so -> libSunshine.so.1.0.0 >>> libsunshine.so.1 -> libsunshine.so.1.0.0 >>> libSunshine.so.1 -> libSunshine.so.1.0.0 >>> libsunshine.so.1.0 -> libsunshine.so.1.0.0 >>> libSunshine.so.1.0 -> libSunshine.so.1.0.0 >>> libsunshine.so.1.0.0 >>> libSunshine.so.1.0.0 >>> Sunshine.so -> libSunshine.so >> >> What's the output of: >> >> ldd -r Sunshine.so >> >> ? >> >>> This happens importing Sunshine, libsunshine, or libSunshine. Looking >>> at the generated sunshine_module_wrapper.cpp file, I see m_name listed >>> as "sunshine". From another thread related to this topic, I >>> understand this import error could be caused by a mismatch between >>> the .so file name and the module name. I tried renaming my module to >>> libSunshine as the OP seemed to have success doing, but still get the >>> import errors using that module name. There are several things I >>> don't understand like the difference between libsunshine.so and >>> libSunshine.so, which have noticeably different sizes. Is name >>> mismatch the cause of the import error or is this something else? >>> >>> I have my latest code up on github if it helps. Thanks. >>> >>> https://github.com/strattonbrazil/Sunshine/tree/dev_pyside_test >>> _______________________________________________ >>> PySide mailing list >>> PySide@lists.pyside.org >>> http://lists.pyside.org/listinfo/pyside >> >> -- >> Hugo Parente Lima >> INdT - Instituto Nokia de Tecnologia _______________________________________________ PySide mailing list PySide@lists.pyside.org http://lists.pyside.org/listinfo/pyside
