Date: Fri, 19 Apr 2019 00:02:34 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 236565] [PATCH] Mk/bsd.port.mk: /etc/make.conf included twice by FreeBSD make Message-ID: <bug-236565-227-yNxH7cMaGF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236565-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236565 --- Comment #5 from rozhuk.im@gmail.com --- (In reply to Mathieu Arnold from comment #4) I play with /usr/src/share/mk/sys.mk / /usr/share/mk/sys.mk __MAKE_CONF=/dev/null must be placed before make called if you already set CFLAGS and other staff. Ports build system prepare all env variables and nothink to load from make.conf at this point. If I put: __MAKE_CONF=/dev/null to /etc/make.conf or in /usr/share/mk/sys.mk after .include "${__MAKE_CONF}" - this does nothing, because importing already done here, and new import will be started after make executed. If I also add: .export __MAKE_CONF / .export-env __MAKE_CONF then this breaks PORTS_MODULES modules build, because they does not load make.conf and have no varibles from parent process. So this must be done only in ports framework to fix ports build. Possible this also should be added to some points in base system to fix doubling CFLAGS during system build. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236565-227-yNxH7cMaGF>