Date: Thu, 26 Sep 2024 17:47:51 +0000 From: bugzilla-noreply@freebsd.org To: uboot@FreeBSD.org Subject: [Bug 281730] sysutils/u-boot-pine64: portmaster failure: : invalid option -- D Message-ID: <bug-281730-39090-DdT1AwJhS6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-281730-39090@https.bugs.freebsd.org/bugzilla/> References: <bug-281730-39090@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281730 --- Comment #3 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Emmanuel Vadot from comment #2) I'll note that if the problem can be replicated with using just make (no portmaster), then in the port's make activity the issue might be tied to: 20240229: AUTHOR: tijl@FreeBSD.org A new command SETENVI that clears the environment and a new variable WRK_ENV that contains a basic environment to use with SETENVI have been added. Ports that run (parts of) the upstream build system directly using commands like "${SETENV} ${MAKE_ENV} ${MAKE_CMD} ..." should change that to "${SETENVI} ${WRK_ENV} ${MAKE_ENV} ${MAKE_CMD} ...". This way the build system runs with a clean environment without interference from the user environment or ports framework environment. Ports can add extra environment variables to WRK_ENV similar to CONFIGURE_ENV, MAKE_ENV, TEST_ENV, and so on, but WRK_ENV is used in all targets while the latter are target-specific. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-281730-39090-DdT1AwJhS6>