Opened 9 years ago
Last modified 9 years ago
#49150 new defect
py34-shiboken fail install or upgrade
Reported by: | watsodw | Owned by: | mamoll (Mark Moll) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | michaelld (Michael Dickens) | |
Port: | py-shiboken |
Description
See log
Attachments (1)
Change History (7)
Changed 9 years ago by watsodw
comment:1 Changed 9 years ago by mf2k (Frank Schima)
Cc: | mmoll@… removed |
---|---|
Owner: | changed from macports-tickets@… to mmoll@… |
Port: | py-shiboken added; py34-shiboken removed |
comment:2 Changed 9 years ago by mamoll (Mark Moll)
comment:3 Changed 9 years ago by mamoll (Mark Moll)
Cc: | michaelld@… added |
---|
comment:4 Changed 9 years ago by michaelld (Michael Dickens)
The issue is not with Qt4, according to the build log. The issue is:
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-shiboken/py34-shiboken/work/shiboken-1.2.2/libshiboken/sbkpython.h:26:10: fatal error: 'Python.h' file not found :info:build #include "Python.h" :info:build ^
So, no idea what's going on there. That said, the QMAKE found is /opt/local/bin/qmake, which is outdated. Please do:
sudo port self update sudo port upgrade outdated
to get the latest ports and such. Updating the outdated ports could take a while, but py*-shiboken should work after that.
comment:5 follow-up: 6 Changed 9 years ago by mamoll (Mark Moll)
You are right. I was trying to reproduce the bug on my machine which is up to date. I don't see the python error, but I get the cmake/Qt4 error.
comment:6 Changed 9 years ago by michaelld (Michael Dickens)
Replying to mmoll@…:
You are right. I was trying to reproduce the bug on my machine which is up to date. I don't see the python error, but I get the cmake/Qt4 error.
I don't see either error :)
If you look through the debug log and the QMAKE environment variable is not set, then something isn't up to date. The latest py*-shiboken includes the qt4 PortGroup, which sets this variable. This variable is then used by find_package to determine the Qt install, at least for the cmake-provided Qt finder.
The problem appears to be that cmake cannot find Qt4. This error is not specific to py34-shiboken. Any cmake based project that includes a line like this will fail: