[1792] in Kerberos_V5_Development

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

Re: On the use of $< in Makefiles...

daemon@ATHENA.MIT.EDU (Barry Jaspan)
Thu Sep 26 12:22:05 1996

Date: Thu, 26 Sep 1996 12:20:56 -0400
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: epeisach@MIT.EDU
Cc: krbcore@MIT.EDU
In-Reply-To: <9609260000.AA01648@kangaroo.mit.edu> (epeisach@MIT.EDU)


   Are we starting to depend on gmake being required again in the build
   system... 

I did not intend to do so.

   %.pl: %.pl.in
	   -rm -f $@.tmp
	   echo "#!$(PERL)" > $@.tmp
	   sed 1d $< >> $@.tmp
	   chmod +x $@.tmp
	   mv $@.tmp $@

I forgot that this was not standard make syntax.  Obviously, this code
is just arranging to have the right path for perl in the #! line at
the top of the scripts.  I'd be perfectly happy with any decent
solution: (1) changing .pl.in to .pl_in and using a standard make
suffix rule, (2) having configure convert from .pl.in to .pl directly,
(3) anything else.  Of course, configure also needs to find the right
path for perl; right now I'm just assuming it is in the standard
execution path.

   (Of course a better question now is which vendor's makes worked with the
   last release and is this a losing battle?)

It should be well known at this point that I think trying to use
vendor make is a waste of time, but I'm going along with it until
everyone else sees the light. :-)

Barry

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