diff options
| author | jlam <jlam@pkgsrc.org> | 2002-08-25 18:51:31 +0000 |
|---|---|---|
| committer | jlam <jlam@pkgsrc.org> | 2002-08-25 18:51:31 +0000 |
| commit | 944ecea87ef2763706362a3d3363358ae1c17f06 (patch) | |
| tree | ca822fd788e4243e2d78f042c6ca3fce4891413a | |
| parent | 4045130092059221edab4c958c5d80b556dfc0b4 (diff) | |
| download | pkgsrc-944ecea87ef2763706362a3d3363358ae1c17f06.tar.gz | |
It's USE_BUILDLINK2, not USE_BUILDLINK2_ONLY.
| -rw-r--r-- | mk/buildlink2/buildlink2.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/mk/buildlink2/buildlink2.txt b/mk/buildlink2/buildlink2.txt index 2d3f130b3d2..9d409b59c4d 100644 --- a/mk/buildlink2/buildlink2.txt +++ b/mk/buildlink2/buildlink2.txt @@ -1,4 +1,4 @@ -$NetBSD: buildlink2.txt,v 1.2 2002/08/22 08:21:29 jlam Exp $ +$NetBSD: buildlink2.txt,v 1.3 2002/08/25 18:51:31 jlam Exp $ The buildlink2 framework is a departure from the original buildlink framework, which tries to do its work up-front before the configure @@ -25,7 +25,7 @@ A: There are several reasons: (1) The new framework makes it simpler to buildinkify a package because we just convert dependencies into including the equivalent - buildlink2.mk files and define USE_BUILDLINK2_ONLY. We don't need + buildlink2.mk files and define USE_BUILDLINK2. We don't need to lie about where libraries or headers we use are installed. (2) All packages using the new framework are strongly buildlinked; it |