Path: utzoo!attcan!uunet!seismo!esosun!cogen!celerity!billd
From: billd@celerity.UUCP (Bill Davidson)
Newsgroups: comp.unix.wizards
Subject: Re: Makefile
Message-ID: <202@celerity.UUCP>
Date: 13 Nov 88 01:35:23 GMT
References: <3165@mipos3.intel.com> <438@auspex.UUCP>
Reply-To: billd@celerity.UUCP (Bill Davidson)
Organization: FPS Computing, San Diego CA
Lines: 36

In article <438@auspex.UUCP> guy@auspex.UUCP (Guy Harris) writes:
>>Is it possible to use the inbuilt commands of the shell
>>from a makefile ? The shell is csh.

[ useful info on shell's in make deleted ]

>lines in the Makefile, using backslashes at the end of the lines to
>continue the command, so that you can put a Bourne shell construct on
>multiple lines:

>	for i in $(MAKEVARIABLE); do \
>		command $$i; \
>	done

>which gets passed to the shell as

>	/bin/sh -c "for i in <expanded Makevariable>; do command $i; done"

>The Bourne shell doesn't mind this; I don't know if the C shell does or
>not. 

Csh does not like this at all.

     Several keywords ("else","endif" and others), must be the FIRST words
on their input lines.  Others must be the only one on their input lines.
     Since make gives ONE line to the shell, this doesn't work too well.
There MUST be some reason for this but I can't begin to figure out what
it could have been.
     I like csh otherwise, but this problem and the I/O redirection
problems keep me in practice with my bourne shell skills.

	--Bill Davidson

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
....!{ucsd|sdcsvax}!celerity!billd