Date: Mon, 10 Jun 2013 10:59:31 -0600 From: Warner Losh <imp@bsdimp.com> To: "Simon J. Gerraty" <sjg@juniper.net> Cc: Chris Rees <crees@FreeBSD.org>, freebsd-toolchain@FreeBSD.org, tech-toolchain@netbsd.org Subject: Re: bmake exports disallowed environment variables Message-ID: <4E8C9D23-FD2B-40FC-B11D-204390F6DD9D@bsdimp.com> In-Reply-To: <20130610163609.8F4D358097@chaos.jnpr.net> References: <CADLo838uS=XqsL576rFFpd21=pzO-eSJjoCQzZcSb0=Vbh70aQ@mail.gmail.com> <20130610163609.8F4D358097@chaos.jnpr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 10, 2013, at 10:36 AM, Simon J. Gerraty wrote:
> 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.
Then perhaps you can share the /bin/sh syntax to unset it?
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E8C9D23-FD2B-40FC-B11D-204390F6DD9D>