Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Sep 2023 02:00:36 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 273938] Environment leakage causes build failures in some ports
Message-ID:  <bug-273938-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273938

            Bug ID: 273938
           Summary: Environment leakage causes build failures in some
                    ports
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Ports Framework
          Assignee: portmgr@FreeBSD.org
          Reporter: grog@FreeBSD.org
                CC: ports-bugs@FreeBSD.org

This bug report is a follow-up on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273490.  In that case,
tex-wb2c failed to build due to something (presumably a variable) inherited
from the environment.  The workaround was to remove all environment and sta=
rt a
new shell:

  $ env -i HOME=3D"$HOME" bash --norc

This is clearly not an isolated case, and finding the variable in question =
is
difficult (I still haven't found mine).  But it should be possible to remove
the environment at the start of the build.  This would affect the deliberate
passing of variables to the build, so it needs some consideration.  This re=
port
is intended as a place holder during discussion.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273938-7788>