[1373] in NetBSD-Development

home help back first fref pref prev next nref lref last post

Re: Recent commits by Derek

daemon@ATHENA.MIT.EDU (Derek Atkins)
Mon Aug 19 15:27:16 1996

To: Greg Hudson <ghudson@MIT.EDU>
Cc: sipb-athena@MIT.EDU
In-Reply-To: Your message of "Mon, 19 Aug 1996 15:18:57 EDT."
             <9608191918.AA09249@small-gods.MIT.EDU> 
Date: Mon, 19 Aug 1996 15:26:18 EDT
From: Derek Atkins <warlord@MIT.EDU>

The problem is that I need to know ATHENA_SYS during *imake*.  There
is no way, as far as I can tell, to look at shell or environment
variables in imake.  So, I modified the Imakefile to pass it to imake
when the Makefile is created.

	* We already require ATHENA_SYS to be set during the build in
	  various modules, so there's no need to avoid using it
	  directly.

It *DOES* use $ATHENA_SYS directly; it is just a way to pass
ATHENA_SYS to imake.  What it does is run:
	imake <normal imake stuff> -DSYS_NAME=${ATHENA_SYS}

If you can think of a better way to pass ATHENA_SYS to imake, I'm all
ears.  But I couldn't think of anything else, and this seemed harmless
enough.  If you know of some other way for Imake to look at
environment variables, please let me know!

	* An important property of a build system is the ability to
	  type "make" in a subdirectory and have it work just as if
	  you had descended into it from above.  Not all of our
	  modules have this property currently (because they were
	  based on already-broken build systems), but that's not an
	  excuse to break it for modules that do have it.

I never broke this!  This still works.  And my changes do not affect
this.  The change I made *ONLY* affects "make Makefiles"...

-derek

home help back first fref pref prev next nref lref last post