Skip to content
Prev 17710 / 63421 Next

looks in liblapack.a not liblapack.so

On Tue, 20 Sep 2005, Charles Geyer wrote:

            
The issue is not the library but whether the code is compiled as
position-independent code (PIC) or not.  Many .a libraries are built
as PIC and they can be used to create shared objects, you just get
copies of the modules you use linked in.  PIC code can be slower,
which is why some prefer to build .a libraries as non-PIC.

I'm not sure why one rarely runs into non-PIC issues on i386--it may
be that gcc at least is always producing PIC code there.  It does come
up on other architectures though, in particular on x86_64.  It seems
that most Linux distros that provide pvm only provide .a libraries,
but some build these with PIC some don't.  Red Hat Enterprise WS4
seems to be non-PIC, FC3 and FC4 seem to be PIC.  If your distro is
non-PIC you will need to build your own PIC version of pvm and tell
rpvm where to find it.

luke