Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#27585 - [vtk] Building VTK fails due to selection of wrong python executable by CMake
Attached to Project:
Community Packages
Opened by Martijn (mvandeg) - Thursday, 15 December 2011, 14:40 GMT
Last edited by Thomas Dziedzic (tomd123) - Thursday, 15 December 2011, 15:13 GMT
Opened by Martijn (mvandeg) - Thursday, 15 December 2011, 14:40 GMT
Last edited by Thomas Dziedzic (tomd123) - Thursday, 15 December 2011, 15:13 GMT
|
DetailsDescription: I hope I report this in the right place, because I actually try to build VTK 5.8.0 from the Arch Building System. When trying to build VTK and both python2 and python3 are installed, Cmake selects python3 (/usr/bin/python) as the python executable.
Additional info: * package version(s): vtk 5.8.0 * config and/or log files etc. Steps to reproduce: Copy PKGBUILD etc. from /var/abs/community/ makepkg -s The error is then: Offending entry: print apply(get_install_path, sys.argv[1:]) This can easily be solved by setting the python executable as a CMake option: -DPYTHON_EXECUTABLE=/usr/bin/python2 in the PKGBUILD file. I am quite new to Arch Linux, so I apologize if I reported this bug in the wrong location/way. Please feel free to contact me if the bug report is not clear. |
This task depends upon
Closed by Thomas Dziedzic (tomd123)
Thursday, 15 December 2011, 15:13 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in svn, will be fixed in the next rebuild
Thursday, 15 December 2011, 15:13 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in svn, will be fixed in the next rebuild
I was building vtk in a chroot which is probably why it was using the python2 executable when I built it.
I will add this option for other's convenience. Thanks!
There is going to be a qt rebuild soon though which I will have to rebuild this package for.
If you want, here is how to get the svn version checked out: http://www.archlinux.org/svn/
Cheers!