cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Seems like we can't avoid REGRESS_ENV/REGRESS_FLAGS.

Browse Source 
Some testsuites use HOME to test their getenv function. Which seems
to be reasonable. But we definitely don't want to allow HOME into
MAKE_ENV by default.
This commit is contained in:
espie 2001-10-07 10:50:47 +00:00
parent 9e6fd66baf
commit e7fbc2b015
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
infrastructure/mk/bsd.port.mk
View File

@ -1,6 +1,6 @@
#-*- mode: Fundamental; tab-width: 4; -*-
# ex:ts=4 sw=4 filetype=make:
FULL_REVISION=$$OpenBSD: bsd.port.mk,v 1.471 2001/10/07 10:47:01 espie Exp $$
FULL_REVISION=$$OpenBSD: bsd.port.mk,v 1.472 2001/10/07 10:50:47 espie Exp $$
# $FreeBSD: bsd.port.mk,v 1.264 1996/12/25 02:27:44 imp Exp $
# $NetBSD: bsd.port.mk,v 1.62 1998/04/09 12:47:02 hubertf Exp $
#
@ -628,6 +628,8 @@ ERRORS+="Missing support for modules ${_m}."
.endfor
REGRESS_TARGET ?= regress
REGRESS_ENV ?= ${MAKE_ENV}
REGRESS_FLAGS ?= ${MAKE_FLAGS}
.if ${FAKE:L} == "yes"
_PACKAGE_COOKIE_DEPS=${_FAKE_COOKIE}
@ -1675,7 +1677,7 @@ ${_REGRESS_COOKIE}: ${_BUILD_COOKIE}
@cd ${.CURDIR} && exec ${MAKE} do-regress
. else
# What REGRESS normally does:
@cd ${WRKBUILD} && exec ${SETENV} ${MAKE_ENV} ${MAKE_PROGRAM} ${MAKE_FLAGS} -f ${MAKE_FILE} ${REGRESS_TARGET}
@cd ${WRKBUILD} && exec ${SETENV} ${REGRESS_ENV} ${MAKE_PROGRAM} ${REGRESS_FLAGS} -f ${MAKE_FILE} ${REGRESS_TARGET}
# End of REGRESS
. endif
. if target(post-regress)