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: <CpLq0y.Fr8@SSD.intel.com>
Sender: usenet@SSD.intel.com
Nntp-Posting-Host: multnomah
Organization: Supercomputer System Division, Intel
References: <RETHINGT.94May4103409@orange.NoDomain>
Date: Tue, 10 May 1994 19:26:57 GMT
Lines: 29


Yep, I've had this same problem, I have a $(HOME)/src/pvm dir I like to
install from, and the install/compilation script insists on the compilation
dir be $(HOME)/pvm. It's kind of annoying...

Rather than hack the install scripts, I made a work around, fool the script
into think it is not where it really is.. I suppose it would be easier to
just make a link, but this is my compilation/install command line...

(zcat pvm3.2.6.tar.Z | tar -xvf -)
(cd pvm3 ; rhome=$HOME ; export $rhome ; $HOME=`pwd` ; export $HOME ; make all ; set $HOME=$rhome ; export $HOME )

The reason it looks so ugly is that it is from an install script I made to
install several software packages on the paragon, with out me needing
to do it manually.

One other problem I've had with pvm (or the paragon, depending on your
point of view), pvm does not compile with pmake, so I have to use regular
make, this is the only software I have come across that disagrees with
pmake, it complains of unknown option jj, what ever that is. Other than
those two problems, pvm compiles and works great.

Tho, I might ask for one enhancement, or just ask a question, why are there
executables in the pvm lib directory??? When I install pvm, I just put these
binaries in /usr/local/bin, and have had no problems. Is there reasoning
behind their being located in the lib dir, or is just something that happened?

-Adam


