diff options
| author | drochner <drochner@pkgsrc.org> | 2011-04-15 17:23:23 +0000 |
|---|---|---|
| committer | drochner <drochner@pkgsrc.org> | 2011-04-15 17:23:23 +0000 |
| commit | 67808816f60c9e248c799096967ed064989044ab (patch) | |
| tree | 2ee03ed90bc3e267d2aed31d8b94164ad2f9c26d /lang/python26 | |
| parent | 770014c54561d5491d4491c35832ca6467d2879c (diff) | |
| download | pkgsrc-67808816f60c9e248c799096967ed064989044ab.tar.gz | |
comment out BUILDLINK_INCDIRS/BUILDLINK_LIBDIRS/BUILDLINK_TRANSFORM
definitions which do things behind the client pkgs back, in particular
manipulate the library search path
It is well possible that this causes some fallout, but I hope it
will be small and can be dealt with on a per-pkg basis.
(partly) suggested by Mark Davies on tech-pkg
Diffstat (limited to 'lang/python26')
| -rw-r--r-- | lang/python26/buildlink3.mk | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/lang/python26/buildlink3.mk b/lang/python26/buildlink3.mk index 6bb7133c079..236d766b0c1 100644 --- a/lang/python26/buildlink3.mk +++ b/lang/python26/buildlink3.mk @@ -1,4 +1,4 @@ -# $NetBSD: buildlink3.mk,v 1.2 2009/09/08 10:06:35 drochner Exp $ +# $NetBSD: buildlink3.mk,v 1.3 2011/04/15 17:23:24 drochner Exp $ BUILDLINK_TREE+= python26 @@ -12,9 +12,9 @@ BUILDLINK_PKGSRCDIR.python26?= ../../lang/python26 BUILDLINK_DEPMETHOD.python26?= ${BUILDLINK_DEPMETHOD.python} . endif -BUILDLINK_INCDIRS.python26+= include/python2.6 -BUILDLINK_LIBDIRS.python26+= lib/python2.6/config -BUILDLINK_TRANSFORM+= l:python:python2.6 +#BUILDLINK_INCDIRS.python26+= include/python2.6 +#BUILDLINK_LIBDIRS.python26+= lib/python2.6/config +#BUILDLINK_TRANSFORM+= l:python:python2.6 .include "../../mk/dlopen.buildlink3.mk" .include "../../mk/pthread.buildlink3.mk" |