Re: wxPython Phoenix build fail ("Could not build python extensions"?) in pyenv 3.5.1 on Linux

Michael Freeman wrote:
> 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

Yes, when building any Python extension module it is important to use
the same Python you are intending to use the built module with.  On your
system "python" is probably a symlink to python2.7 and the command
"python3" to the python3.5 binary.  Look at `ls -l /usr/bin/python*` to
check.

>
> 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).

You shouldn't need to.  The main demo starts up with just a small-ish
app and doesn't load the rest of the demo modules until they are
selected.  If it was stuck then something unexpected is happening and it
would be good to investigate it.


-- 
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.