> -----Original Message-----
> From: lam-bounces_at_[hidden]
> [mailto:lam-bounces_at_[hidden]] On Behalf Of Dennis van Dok
> Sent: Thursday, July 06, 2006 8:19 AM
> To: General LAM/MPI mailing list
> Subject: Re: LAM: liblam.so is not linked to libutil on Linux
>
> >The @LIBS@ here should already have "-lutil" in it because
> it was added
> >during the same AC_CHECK_LIB as when LIBLAM_EXTRA_LIBS got "-lutil".
> >
> Yeah, well, right below it says:
>
> LIBS="$libs_SAVE"
Right, duh.
[Jeff reaches for more caffeine]
> 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.
Is there a reason that you did not use the wrapper compilers to create
Rmpi, btw? Using the wrapper compilers should automatically add -lutil
for you. Alternatively, you can use the --showme option to extract the
flags that the wrappers add and invoke the underlying compiler yourself,
etc.
--
Jeff Squyres
Server Virtualization Business Unit
Cisco Systems
|
