Newsgroups: comp.parallel.pvm
Path: ukc!uknet!EU.net!uunet!ssd.intel.com!eros
From: eros@ssd.intel.com (Adam E. Harrison)
Subject: Re: $HOME Dependency
Message-ID: <Cq2JEF.677@SSD.intel.com>
Sender: usenet@SSD.intel.com
Nntp-Posting-Host: modi
Organization: Supercomputer System Division, Intel
References: <RETHINGT.94May4103409@orange.NoDomain> <CpLq0y.Fr8@ssd.intel.com> <2qpm44$jg6@play.cs.columbia.edu>
Date: Thu, 19 May 1994 21:23:02 GMT
Lines: 17

cheah@news.cs.columbia.edu (Po Shan Cheah) writes:

}In article <CpLq0y.Fr8@ssd.intel.com>,
}When you say you put the binaries in /usr/local/bin, I hope you mean
}you are putting the shell scripts in /usr/local/bin. Those executable
}files you see in ~/pvm/lib are actually shell scripts that use
}pvmgetarch to determine which architecture they are running on and
}then run the appropriate binaries in ~/pvm/lib/SUN4 or ~/pvm/lib/HPPA
}or whatever. This allows you to use pvm the same way on a network of
}different types of machines which all have that directory mounted in
}the same place.

If you do a "make all", you will end up with ~/pvm/lib/$ARCH/pvmd3 and
~/pvm/lib/$ARCH/pvm. I don't believe these really belong in the lib directory.
I was courious as to why they are there...

-Adam

