#18906: qtiplot build fails ----------------------------------+----------------------------------------- Reporter: jwhowse4@… | Owner: jonas@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: qtiplot ----------------------------------+----------------------------------------- Comment(by jonas@…): Replying to [comment:8 gnwiii@…]:
Some python scripts used to configure qtiplot have #!/usr/bin/python, so those who have installed SIP and PyQt (as described in the qtiplot docs) in the "System" python won't see this problem:
$ cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_aqua_qtiplot/work/qtiplot-0.9.7.6/qtiplot" nashi:qtiplot gwhite$ head -1 *.py
==> python-includepath.py <== #!/usr/bin/python
==> python-libs-win.py <== #!/usr/bin/python
==> python-sipcmd.py <== #!/usr/bin/python
That's indeed strange. I have exactly the same shebangs and executing `python-includepath.py` also returns `/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5` here. However, the compiler commandline contains `-I/opt/local/include/python2.5`. So, my guess is that the buildsystem doesn't execute this script but calls `python` (from PATH) with it. In that case, sed'ing these python scripts to adapt the shebang won't help. Am I correct that `which python` returns `/usr/bin/python` on your system? Please use `python_select` (you may have to install this port first) to make macport's python25 the default python. Hopefully that does the trick. -- Ticket URL: <http://trac.macports.org/ticket/18906#comment:11> MacPorts <http://www.macports.org/> Ports system for Mac OS