From add2442ee0095dc702abe5b79ff201b0bf1ea2d5 Mon Sep 17 00:00:00 2001 From: jlam Date: Sun, 25 Aug 2002 18:51:31 +0000 Subject: It's USE_BUILDLINK2, not USE_BUILDLINK2_ONLY. --- mk/buildlink2/buildlink2.txt | 4 ++-- 1 file 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 -- cgit v1.2.3