Newsgroups: comp.parallel.pvm
From: jmartin@bailer.cs.uiowa.edu (Jeffrey Martin)
Subject: pvm shared libs
Organization: The University of Iowa, Iowa City, Iowa, USA
Date: 25 Jun 1996 15:37:48 -0500
Message-ID: <k6g4tnz39ib.fsf@bailer.cs.uiowa.edu>

I'm tinkering with pvm to make it produce shared libs (not hard so
far), and was wondering what is the difference between libpvm3 and
libpvm3s on shared memory machines? (and no, I don't want an entire
ton of tk stuff) Some shared memory stuff seems to go into libpvm3
(lpvmshmem - "Libpvm core for MPP environment" & pvmshmem -
"Shared-memory stuff"), while other shared memory stuff seems to go
into libpvm3s (pvmdabuf - "Data buffer manip")...

Wouldn't it be simplier to make one library with all the functions
needed? What would break by doing so?

Jeff

p.s. As an aside, what do the above listed files do? While my SGI5 is
capable of using shared mem, it isn't compiled into the library code?
How do processes communicate on a single (non-mp) machine?

p.s.s. Most of the changes so far could well be done in general, and
break nothing so far, such as using -L and -l instead of feeding in an
archive name, and using absolute paths instead of ../ constructs.

