Subject: Re: make should unset $ENV
To: Todd Vierling <>
From: Simon J. Gerraty <>
List: tech-toolchain
Date: 08/01/2003 10:29:06
On Fri, 1 Aug 2003 07:41:34 -0400 (EDT), Todd Vierling writes:
>On Fri, 1 Aug 2003, Simon J. Gerraty wrote:
>: Both our /bin/sh and ksh will use the file pointed to by $ENV as a
>: startup script (like csh's .cshrc).  It occurs to me that any build
>: that relies on $ENV being set and doing something is in serious
>: trouble.
>Really?  ISTM that your $ENV script is ill-behaved if it futzes with make.
>I have set ENV=$HOME/.shrc for years now with no ill effect on make(1).

Correct.  My $ENV doesn't interfere in anyway - nor should any sanely
written one.  My point is that no build should rely on $ENV causing a
shell to do anything.  Now, because you & I have a sane $ENV script
does not mean everyone does.  One of the reasons I added the
MAKE_PRINT_VAR_ON_ERROR functionality was to help diagnose reported
build breaks.  Knowing that $ENV _cannot_ be a factor is handy.