summaryrefslogtreecommitdiff
path: root/lang/python27/buildlink3.mk
diff options
context:
space:
mode:
authordrochner <drochner>2011-04-15 17:23:23 +0000
committerdrochner <drochner>2011-04-15 17:23:23 +0000
commit89df40b97d66c99131e466064dfc36021b89050a (patch)
tree2ee03ed90bc3e267d2aed31d8b94164ad2f9c26d /lang/python27/buildlink3.mk
parent8517d9ede6a6b1427915fb62f2f6298c368f6653 (diff)
downloadpkgsrc-89df40b97d66c99131e466064dfc36021b89050a.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/python27/buildlink3.mk')
-rw-r--r--lang/python27/buildlink3.mk8
1 files changed, 4 insertions, 4 deletions
diff --git a/lang/python27/buildlink3.mk b/lang/python27/buildlink3.mk
index 5de88e1b7ca..92686ad6b23 100644
--- a/lang/python27/buildlink3.mk
+++ b/lang/python27/buildlink3.mk
@@ -1,4 +1,4 @@
-# $NetBSD: buildlink3.mk,v 1.2 2011/02/22 10:50:37 adam Exp $
+# $NetBSD: buildlink3.mk,v 1.3 2011/04/15 17:23:24 drochner Exp $
BUILDLINK_TREE+= python27
@@ -12,9 +12,9 @@ BUILDLINK_PKGSRCDIR.python27?= ../../lang/python27
BUILDLINK_DEPMETHOD.python27?= ${BUILDLINK_DEPMETHOD.python}
.endif
-BUILDLINK_INCDIRS.python27+= include/python2.7
-BUILDLINK_LIBDIRS.python27+= lib/python2.7/config
-BUILDLINK_TRANSFORM+= l:python:python2.7
+#BUILDLINK_INCDIRS.python27+= include/python2.7
+#BUILDLINK_LIBDIRS.python27+= lib/python2.7/config
+#BUILDLINK_TRANSFORM+= l:python:python2.7
.include "../../mk/dlopen.buildlink3.mk"
.include "../../mk/pthread.buildlink3.mk"