Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] Open MPI 1.2.4 verbosity w.r.t. osc pt2pt
From: Brian W. Barrett (brbarret_at_[hidden])
Date: 2007-12-13 18:01:32

On Thu, 13 Dec 2007, Jeff Squyres wrote:

> Specifically: it would probably require some significant hackery in
> the OMPI build process to put in a #define that indicates whether OMPI
> is being built statically or not. But the AM/LT process shields this
> information from the build process by design (part of the issue is
> that AM/LT allows both static and shared libraries to be built
> simultaneously). We'd then have to introduce some global symbol that
> could be queried that is outside of the MPI interface. Neither of
> these things are attractive. :-(

Well, if libmpi.a is static, then this whole conversation is pointless
because you're not going to dlopen it in the first place.

But it is easy for OPen MPI to figure out whether it's statically or
dynamically linked, as libtool compiles the code twice if building both
static and shared and you could poke at #defines to figure out what's
going on -- easy enough to deal with. I just don't think we should be
doing so :).