Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!zephyr.ens.tek.com!tektronix!sequent!mntgfx!lisch From: lisch@lisch.mentor.com (Ray Lischner) Newsgroups: comp.sys.apollo Subject: Re: an NCS distributed make utility ? Message-ID: Date: 7 May 90 19:07:49 GMT References: <20680@boulder.Colorado.EDU> <1828@cernvax.UUCP> Sender: lisch@mentor.com (Ray Lischner) Distribution: comp Organization: Mentor Graphics Corp., Beaverton, OR Lines: 26 In-reply-to: hedman@cernvax.UUCP's message of 5 May 90 16:37:23 GMT In article <1828@cernvax.UUCP> hedman@cernvax.UUCP (fredrik hedman) writes: >I have just compiled version 3.58 of the GNU make program on an apollo. >This version of 'make', which by the way has the best documentation of >the 'make' tool I have ever read, supports ... >I have not yet figured out how to use 2) above, anyone else ? I am trying to implement remote makes for Apollos. A good solution is to run a make server on each node, and a local make could communicate with the servers to decide where to run a program. In our environment, however, this does not work because I cannot run a server process on other people's nodes. Instead, the user supplies a list of nodes. Make examines the load averages on the nodes until it finds a suitable one, then it runs the program there. The problem is that there does not seem to be a clean way to export the environment variables to the remote make. Until I can overcome this problem, my remote make implementation is worthless. I am interesting in knowing if others have tried or succeeded in implementing remote makes, or if anyone has any suggestions. -- Ray Lischner UUCP: {uunet,apollo,decwrl}!mntgfx!lisch -- Ray Lischner UUCP: {uunet,apollo,decwrl}!mntgfx!lisch