Date: Mon, 10 Jun 2013 09:36:09 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Chris Rees <crees@FreeBSD.org> Cc: freebsd-toolchain@FreeBSD.org, tech-toolchain@netbsd.org, sjg@juniper.net Subject: Re: bmake exports disallowed environment variables Message-ID: <20130610163609.8F4D358097@chaos.jnpr.net> In-Reply-To: <CADLo838uS=XqsL576rFFpd21=pzO-eSJjoCQzZcSb0=Vbh70aQ@mail.gmail.com> References: <CADLo838uS=XqsL576rFFpd21=pzO-eSJjoCQzZcSb0=Vbh70aQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Chris,
>bmake appears to export ${.MAKE.LEVEL} into the environment, which sh
>doesn't support, due to the leading '.'. Normally this is ignored,
Yes, though env(1) does allow it. The leading '.' was deliberately chosen
to reduce the risk of this being picked up from user environment.
That is, if make finds .MAKE.LEVEL in its environment, then it "trusts"
it - either an ancestor was make (rather than say gmake), or the user
"must know what they are doing".
In short, I'd like to leave it as is.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130610163609.8F4D358097>