From nobody Sat Jan 20 19:39:58 2024
X-Original-To: python@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4THRdq3Gyhz57Ljg
for <python@mlmmj.nyi.freebsd.org>; Sat, 20 Jan 2024 19:39:59 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
client-signature RSA-PSS (4096 bits) client-digest SHA256)
(Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4THRdq26R7z4lNs
for <python@FreeBSD.org>; Sat, 20 Jan 2024 19:39:59 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org;
s=dkim; t=1705779599;
h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
to:to:cc:mime-version:mime-version:content-type:content-type:
content-transfer-encoding:content-transfer-encoding;
bh=Z9To010piAgDvRKJWOp3Q6cPXHf0ZMhWgZqj5JNrYGU=;
b=bYRLYoK4MWi56TVE/3aWi4HhjOOnc5AJ5sptkGRGVFy+MPaWdhy+AwATEWK3JFYCdR7KS7
2lv5d1Fyk5xiVDDwQwllXMIZNBvcv0nq0dOmiu4IojkEYek9RE7PetBN+8DBs39dgkeMqX
Ck+MMG7IpxF8rkabTaWJ/7Pct0+0eLbKfU38daADCEyHuA+Sr3GuMCsiPufFk4UGlNU3Qe
40BZH7MLHbOUGm5Gs3ysTj/I5Je+bMRJGVM3XbmcB/gXh2ndurQPX1F+aL+26ThX/XMsZD
ovTU8osSembSgQ5ubi7oLJtDXyXKChe9pPndTBbvNvMpxNl7kJKnwjA+R/PlTg==
ARC-Authentication-Results: i=1;
mx1.freebsd.org;
none
ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1705779599; a=rsa-sha256; cv=none;
b=jwjsSUJFgBF5u8flrnGa+D6493o3i5CSPfosPmKwAaZ/c+b6ybAms/exOKMVXpzxK/mpMZ
qLXtuYy/+V4ScUFuYdkjymaZJ02JiOeKvim+bBgUl3sy5pvayZChay8gKO6wJSyR9PlvwT
d/uu5RXjNQ1ED/KUKLbW17060nGjatacNywCg26azZLezroMMnGLgHEjyUlVAsNE06QSCU
e0rys1fM85bgBBCwNFuTSMOC6Xp8+uYOOOSKpSoTdXrQLzhO4MTUSYJTYOpagfaykBuWrZ
ciAx1ntHr5GAeC/OiSuSeBXUAluJFoeNdNlUa1od2aBtT0tUJBer4Yviktwb4g==
Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
(Client did not present a certificate)
by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4THRdq14pCznYQ
for <python@FreeBSD.org>; Sat, 20 Jan 2024 19:39:59 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.5])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 40KJdxkV062538
for <python@FreeBSD.org>; Sat, 20 Jan 2024 19:39:59 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 40KJdxSC062536
for python@FreeBSD.org; Sat, 20 Jan 2024 19:39:59 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: python@FreeBSD.org
Subject: [Bug 276478] Mk/*: Build with a clean environment
Date: Sat, 20 Jan 2024 19:39:58 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Ports Framework
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: tijl@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution:
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: portmgr@FreeBSD.org
X-Bugzilla-Flags: exp-run?
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
op_sys bug_status bug_severity priority component assigned_to reporter cc
blocked flagtypes.name attachments.created
Message-ID: <bug-276478-21822@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-python
List-Help: <mailto:python+help@freebsd.org>
List-Post: <mailto:python@freebsd.org>
List-Subscribe: <mailto:python+subscribe@freebsd.org>
List-Unsubscribe: <mailto:python+unsubscribe@freebsd.org>
Sender: owner-freebsd-python@freebsd.org
X-BeenThere: freebsd-python@freebsd.org
MIME-Version: 1.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276478
Bug ID: 276478
Summary: Mk/*: Build with a clean environment
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Ports Framework
Assignee: portmgr@FreeBSD.org
Reporter: tijl@FreeBSD.org
CC: acm@FreeBSD.org, amdmi3@FreeBSD.org,
gnome@FreeBSD.org, go@FreeBSD.org,
haskell@FreeBSD.org, java@FreeBSD.org,
kde@FreeBSD.org, olgeni@FreeBSD.org, perl@FreeBSD.org,
ports-bugs@FreeBSD.org, python@FreeBSD.org,
ruby@FreeBSD.org, rust@FreeBSD.org, x11@FreeBSD.org
Blocks: 272216
Flags: exp-run?
Created attachment 247801
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D247801&action=
=3Dedit
patch
Both our make and gmake use the MAKEFLAGS environment variable but the valu=
es
aren't compatible and the latest version of gmake complains about that. To
prevent that environment variables interfere with the build process like th=
is,
this patch adds a new command SETENVI=3D/usr/bin/env -i that clears the
environment. The idea is to use SETENVI instead of SETENV when running bui=
ld
tools and scripts so their environment only contains variables from
CONFIGURE_ENV or MAKE_ENV or TEST_ENV or similar. This way it doesn't matt=
er
what variables our make uses or what environment variables a user might have
set.
This patch takes care of Mk/* and Mk/Uses/*. Individual ports can be chang=
ed
later.
If you are the maintainer of any of the Mk/Uses/* files please review the
changes.
A minor open problem is that the TERM environment variable is now missing w=
hich
means that error messages are no longer colored for instance. I'd like to
introduce a new variable WRK_ENV that would contain common environment
variables like TERM, PATH, and SHELL, and perhaps other variables that are
common between CONFIGURE_ENV and MAKE_ENV. It would be used in every make
target while CONFIGURE_ENV, MAKE_ENV, and TEST_ENV contain target specific
environment variables. Any objections to this?
Referenced Bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272216
[Bug 272216] devel/gmake: Update to 4.4.1
--=20
You are receiving this mail because:
You are on the CC list for the bug.=