Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!crdgw1!crdos1!davidsen From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr) Newsgroups: comp.unix.questions Subject: Re: Problem with make Summary: Two possible solutions Keywords: make for sysV Message-ID: <656@crdos1.crd.ge.COM> Date: 29 Sep 89 23:18:31 GMT References: <715@bbking.KSP.Unisys.COM> <11169@smoke.BRL.MIL> <1989Sep29.164831.26616@wash08.uucp> Reply-To: davidsen@crdos1.UUCP (bill davidsen) Organization: GE Corp R&D Center Lines: 37 In article <1989Sep29.164831.26616@wash08.uucp>, rae98@wash08.uucp (Robert A. Earl) writes: | Alternatively, can you pass args through make to be used in the makefile? | What I really want to do is: | | make tar (system_name) | and have the makefile generate a tar file and send it to system_name. | | the tar is easy.....any way to do the rest? I have several thoughts which may work or give you inspiration. If the number of systems is small you could have a makerule for each. Alternatively you can specify the system name as a parameter on the make command line. $ make tar SYSNAME=wimpy where the makefile has somthing like: # make tar here # # now send it to the remote, your favorite way rsh $(SYSNAME) cat ">/spool/new.tar" < tar # also you can: # uucp tar $(SYSNAME)!~/tarspool/new.tar If you don't need an interactive prompt you may be able to do this. The nice thing is that it can go in a script to run offhours. $ for sys in wimpy popeye olive sweetp > do make tar SYSNAME=$sys > done -- bill davidsen (davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen) "The world is filled with fools. They blindly follow their so-called 'reason' in the face of the church and common sense. Any fool can see that the world is flat!" - anon