Re: wxPython Phoenix build fail ("Could not build python extensions"?) in pyenv 3.5.1 on Linux
Michael Freeman <[email protected]>
| Newsgroups | gmane.comp.python.wxpython.devel |
|---|---|
| Message-ID | <[email protected]> |
Apologies for the repeated replies, but you'll be glad to know that I finally got it working ! Screenshot: http://files.djbarney.org/blender_dj_turntable_wxPython_Phoenix_LINUX_file_open.png The last error was due to something to do with having to use "python3" not "python" for the compilation for a reason I don't pretend to understand. Here is the description of the same issue someone else had: http://stackoverflow.com/questions/36723206/cython-compilation-error-dynamic-module-does-not-define-module-export-function So that made the build command: /opt/python3.5.1/bin/python3.5 build.py -j 7 dox etg --nodoc sip build 2>&1 | tee phoenix_build_output.txt Demo's appear to run OK (apart from "demo.py" which get's stuck with 100% cpu usage but I assume it's huge and did not wait for completion). So thanks for the help, it's been fun but a HUGE saga for me (long story). If I can help building wheel's for distribution in any way then please say. Cheers Michael Z Freeman On Monday, September 5, 2016 at 7:34:46 PM UTC+1, Robin Dunn wrote: > > Michael Freeman wrote: > > So Blender loads up OK using the "pyenv" Python, but both the build I > > did in "pyenv" *AND* the build to a wheel in "venv" (the wheel install > > replaced the pip built version) throws this error ... > ... > > > from ._core import * > > ImportError: > > > /home/michaelzfreeman/Downloads/blender-2.77-a5261e0-linux-glibc219-x86_64/2.77/python/lib/python3.5/site-packages/wx/_ > core.cpython-35m-x86_64-linux-gnu.so: > > symbol _ZNK8wxWindow7IsShownEv, version WXU_3.0 not defined in file > > libwx_gtk2u_core-3.0.so.0 with link time reference > > Does the same thing happen if you import wx in a Python session (which > has your Phoenix wheel installed) outside of the Blender environment? > (I wasn't sure if this is what you meant in the second half of your > opening statement above.) > > Errors like this could happen if the system is loading the wrong version > of a shared library, for example if it loads a lib different than the > one it was linked with at build time. On linux you can use the ldd > command to determine where shared libraries are coming from, try this: > > ldd > > /home/michaelzfreeman/Downloads/blender-2.77-a5261e0-linux-glibc219-x86_64/2.77/python/lib/python3.5/site-packages/wx/_ > core.cpython-35m-x86_64-linux-gnu.so > > and there should be a line in the output that shows the full path to the > libwx_gtk2u_core-3.0.so.0 it is loading. For a normal Phoenix build > (without flags telling it to use a different wxWidgets or etc.) then it > should use the libwx_* files in the same folder as the Phoenix extension > modules. If it does show it using that lib then perhaps Blender is > setting something in the environment that is preventing the dynamic > loader from using the rpath set in the Phoenix modules, and it is > looking in the system or Blender libs location or something instead. So > if you can repeat that command inside of Blender somehow then that may > give some clues as well. > > > > This could be a build flag: "wxPython-dev › wxpython-3.0.0.0 and > > libnotify" - > > https://groups.google.com/forum/#!topic/wxpython-dev/DGMlB7Gi4ss > > <https://groups.google.com/forum/#%21topic/wxpython-dev/DGMlB7Gi4ss> > > The missing symbol doesn't have anything to do with the libnotify > functionality. > > > -- > Robin Dunn > Software Craftsman > http://wxPython.org > -- You received this message because you are subscribed to the Google Groups "wxPython-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.