diff options
| author | dsainty <dsainty@pkgsrc.org> | 2014-05-19 22:44:14 +0000 |
|---|---|---|
| committer | dsainty <dsainty@pkgsrc.org> | 2014-05-19 22:44:14 +0000 |
| commit | 3112b816f01ddd4287153c777308fe7092d432d9 (patch) | |
| tree | 5e67c5bc3ca6c27527e361f92cac2ea8dc4789e5 /devel/libftdi1 | |
| parent | 7d16eccf99eca2733d5e90562c0a4ade75b9d387 (diff) | |
| download | pkgsrc-3112b816f01ddd4287153c777308fe7092d432d9.tar.gz | |
The package uses the "python" executable for building the python bits. If it
isn't present in the package build sandpit it may reach out and use a possibly
unmanaged version of python. On Linux that might be some base system copy of
python, which would only be the same version by chance.
If it happens to be, say, python 2.6 - but Pkgsrc is defaulting to python 2.7,
then the installed files will have the wrong filenames, the PLIST won't match,
and the build will fail (not to mention that the built files may well be
incompatible with the intended python anyway).
Having the "python" tool in the sandpit solves this problem.
Diffstat (limited to 'devel/libftdi1')
| -rw-r--r-- | devel/libftdi1/Makefile | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/devel/libftdi1/Makefile b/devel/libftdi1/Makefile index 51c4764adc7..84798d144c1 100644 --- a/devel/libftdi1/Makefile +++ b/devel/libftdi1/Makefile @@ -1,4 +1,4 @@ -# $NetBSD: Makefile,v 1.3 2014/05/09 07:37:00 wiz Exp $ +# $NetBSD: Makefile,v 1.4 2014/05/19 22:44:14 dsainty Exp $ DISTNAME= libftdi1-1.0 CATEGORIES= devel @@ -50,5 +50,6 @@ do-configure: .include "../../devel/swig/buildlink3.mk" .include "../../lang/python/pyversion.mk" .include "../../lang/${PYPACKAGE}/buildlink3.mk" +.include "../../lang/python/tool.mk" .include "../../mk/bsd.pkg.mk" |