aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorgrembo <grembo@FreeBSD.org>2014-05-24 22:05:30 +0800
committergrembo <grembo@FreeBSD.org>2014-05-24 22:05:30 +0800
commitf14ed12f778125c38b91e1bf73f1c080a440d077 (patch)
treec6bb10ab67e571630832b4b440b31e0aec45aee8
parent3e762d6682b2b3fb1bb42f351b74a13c5b488ae5 (diff)
downloadfreebsd-ports-gnome-f14ed12f778125c38b91e1bf73f1c080a440d077.tar.gz
freebsd-ports-gnome-f14ed12f778125c38b91e1bf73f1c080a440d077.tar.zst
freebsd-ports-gnome-f14ed12f778125c38b91e1bf73f1c080a440d077.zip
It turns out that cmake is still using gmake during the configure
phase, even though build is then done using make(1). If gmake is not available on the host, cmake falls back to make(1) to configure and the resulting Makefiles won't work on either, make or gmake. Therefore I'll rollback to using gmake all the time. Reviewed by: flo (mentor) Approved by: flo (mentor)
-rw-r--r--databases/mariadb55-server/Makefile2
1 files changed, 1 insertions, 1 deletions
diff --git a/databases/mariadb55-server/Makefile b/databases/mariadb55-server/Makefile
index b03ac49f46d5..151da7194894 100644
--- a/databases/mariadb55-server/Makefile
+++ b/databases/mariadb55-server/Makefile
@@ -22,7 +22,7 @@ SUB_FILES= pkg-message
PKGMESSAGE= ${WRKDIR}/pkg-message
SLAVEDIRS= databases/mariadb55-client
-USES= cmake shebangfix
+USES= cmake gmake shebangfix
SHEBANG_FILES= scripts/*.sh
NO_OPTIONS_SORT=yes