> My point is that no build should rely on $ENV causing a shell to do
> anything.

If you mean "build" as in "rebuild NetBSD", you're right - and if that
were all make were ever used for, your change would be right.

But make is used for _far_ more than that, and for normal user use
(most users won't be rebuilding the system, after all), unsetting ENV
is a very wrong thing to do because it gives make-executed commands a
mysteriously different environment from user-issued commands.  My
comparison to resetting or unsetting PATH was entirely serious.

Unsetting ENV *for an OS build* is sensible - but make is not the place
to do it.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B