Jeff Squyres (jsquyres) wrote:
>Right, duh.
>
>[Jeff reaches for more caffeine]
>
>
Hey, it's still the July 4th aftermath :-)
>>Confirmed. I think you don't want it in there in general,
>>because LIBS
>>is global for the entire build.
>>
>>
>
>You're absolutely right -- I just wasn't awake enough to see the
>ramifications.
>
>What threw me was how this could have worked at all without your patch.
>Digging into the LAM source a little more, I see that we added
>@LIBLAM_EXTRA_LIBS@ to every place that we also linked liblam. But I
>can see how this would not help external packages that do not use the
>LAM wrapper compilers.
>
>
Exactly. I think I just added -lutil myself at an earlier stage.
>Is there a reason that you did not use the wrapper compilers to create
>Rmpi, btw?
>
Well, that has to do with the way Rmpi is distributed. It is a source
tarball with a configure script, but you are supposed to feed it to R by
saying 'R CMD INSTALL Rmpi_0.5-2.tar.gz
--configure-args="--with-mpi=/opt/lam"' and it will build and install it
for you as a local R package.
I suppose I could pass the hint to the Rmpi maintainer to work this into
the configure script.
My point is that dynamic linking of shared libraries should be used, if
supported. I believe that e.g. Solaris doesn't.
Regards,
Dennis
--
D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.vl-e.nl
|
