On Wed, 8 May 2002, Greg A. Woods wrote:

> Ah yes -- thanks for the reminder!  This has bugged me from the very
> first day I ever encountered Python, and I seem to have to remember
> this "quirk" to their build system every single time I try it again.
>
> 	$ echo $OPT
> 	/opt

...

> <SOAPBOX>
> Sometimes it really sucks when a build system uses environment variables
> for things other than where they're normally used (eg. $PATH is OK,
> other random junk like $OPT is not).  Make has its own "variables" --
> why do we have to continually confuse them with environment variables?!?!?!
> It's even worse when the "./configure" succeeds, but the 'make' fails.
> </SOAPBOX>

But note that "pkgsrc" already wraps the "make" and "configure" steps
with ${SETENV} (==/usr/bin/env) followed by all the variables that are
supposed to get passed in. Maybe we should rather set ${SETENV} to
"env -i"?

Frederick