summaryrefslogtreecommitdiff
path: root/security/libgpg-error
diff options
context:
space:
mode:
authorjschauma <jschauma>2005-05-15 22:22:48 +0000
committerjschauma <jschauma>2005-05-15 22:22:48 +0000
commit380c16a29dc2ff8309af598d94468d138a22db74 (patch)
tree2be8eec88797d8130cb57fd148d4940e83e50eb3 /security/libgpg-error
parentd30eb875816456abc7e5be617dcc8b35e38dea4e (diff)
downloadpkgsrc-380c16a29dc2ff8309af598d94468d138a22db74.tar.gz
Unbreak this under IRIX by not demanding gawk. This is a hack:
Apparently, for as of yet undetermined reasons, gawk as built on IRIX under pkgsrc croaks on regular expressions including a combination of alpha- and numerical matches, such as the rather trivial /^[ \t]*[0-9]+/ Let's use the system's AWK (ie nawk) for this package to avoid breaking hundreds of dependents. Speculation: somehow the regular expression library used to build gawk conflicts with the systems regular expression library or some such. Note: gawk from SGIs freeware collection depends on expat -- why is that? Does that have anything to do with anything?
Diffstat (limited to 'security/libgpg-error')
-rw-r--r--security/libgpg-error/Makefile8
1 files changed, 7 insertions, 1 deletions
diff --git a/security/libgpg-error/Makefile b/security/libgpg-error/Makefile
index 17b65edeadb..73300eaf2ef 100644
--- a/security/libgpg-error/Makefile
+++ b/security/libgpg-error/Makefile
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile,v 1.10 2005/04/11 21:47:13 tv Exp $
+# $NetBSD: Makefile,v 1.11 2005/05/15 22:22:48 jschauma Exp $
#
DISTNAME= libgpg-error-1.0
@@ -14,7 +14,13 @@ PKG_INSTALLATION_TYPES= overwrite pkgviews
USE_LIBTOOL= YES
GNU_CONFIGURE= YES
USE_PKGLOCALEDIR= YES
+
+.include "../../mk/bsd.prefs.mk"
+
+# XXX See HACKS
+.if ${OPSYS} != IRIX
USE_GNU_TOOLS+= awk
+.endif
MAKE_ENV+= LC_ALL="C"