Date: Mon, 10 Jun 2013 10:42:34 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Warner Losh <imp@bsdimp.com> Cc: Chris Rees <crees@FreeBSD.org>, freebsd-toolchain@FreeBSD.org, tech-toolchain@netbsd.org, sjg@juniper.net Subject: Re: bmake exports disallowed environment variables Message-ID: <20130610174234.6539158097@chaos.jnpr.net> In-Reply-To: <4E8C9D23-FD2B-40FC-B11D-204390F6DD9D@bsdimp.com> References: <CADLo838uS=XqsL576rFFpd21=pzO-eSJjoCQzZcSb0=Vbh70aQ@mail.gmail.com> <20130610163609.8F4D358097@chaos.jnpr.net> <4E8C9D23-FD2B-40FC-B11D-204390F6DD9D@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 10 Jun 2013 10:59:31 -0600, Warner Losh writes: >Then perhaps you can share the /bin/sh syntax to unset it? No, the point is that this variable is not supposed to be manipulated by sh at all. The name was chosen precisely because it cannot easily be put into the environment. That and it "looks" like a make internal variable - which it is.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130610174234.6539158097>