If it is required for the running of the finished package, it should be in the depends array. If it is only required for the building of the final package, it should be in the makedepends array. If it is required for building and/or optionally required for the final package, it should be in the makedepends and optdepends arrays.
I used the makedepends array and that solved the issue.
Thank you!
]]>Have you got python listed as a dependency or make-dependency in the PKGBUILD?
No.
I didn't think "depends" applied in this case.
I interpreted it as a dependancy nessary to run on the installed system rather than to the build process.
Do I just specify 'python' in the depends array?
Edit: actually the scripts runs under both version. - Tried that.
]]>EDIT: Assuming that python 3 is the python that the script requires. If at all possible, you should petition the developers/maintainers of the script to be less ambiguous. "/usr/bin/env python" will result in a python 2 or python 3 interpreter, depending on which system you're using. Arch uses python 3 as "python". If the script requires python 2, you will need to modify the shebang (using sed in the PKGBUILD, for example) to reflect this. Unless you can get the change made upstream, of course.
]]>sudo makechrootpkg -c -r $CHROOT
. . .
==> Starting build()...
/usr/bin/env: python: No such file or directory
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Build failed, check /home/xxx/chroot/xxx/build
The offending script:
configure.py: #! /usr/bin/env python
PKGBUILD contains:
build() {
cd "$srcdir/$pkgname-$pkgver"
./configure.py
make
}
The package will build if I omit the python script.
It just looks at cpuinfo and optimizes the build flags.
Any help appreciated!
]]>