Jeff and everyone else I contacted about this: thanks for helping track
down the problem. I've been beating my head on this for a few days and
don't have the library experience to have caught these nuances. Thanks
again!
-- Nathan
Correspondence
--
On Sep 15, 2005, at 4:32 PM, Jeff Squyres wrote:
This allows the components themselves to pull in shared libraries when
they are dlopened -- if they need to. If the symbols can be resolved
in the parent process' public symbol namespace, they still will be (as
in the standalone executable exampl
Followup for the list... a bit of explanation of Nathan's problem about
shared libraries and unresolved symbols.
Short version:
--
It's an OMPI bug when built as a shared library (not an issue for
static libraries). The fix is straightforward, but involves grunt
work. I'll try t
Hi Nathan,
> Nathan DeBardeleben writes:
> >
> > I've been having this problem for a week or so and I've been asking
> > other people to weigh in if they know what I'm doing wrong. I've gotten
> > no where on this so I figure I'll finally drop it out on the list.
> > First, here's the importa
Hi Nathan,
Nathan DeBardeleben writes:
I've been having this problem for a week or so and I've been asking
other people to weigh in if they know what I'm doing wrong. I've gotten
no where on this so I figure I'll finally drop it out on the list.
First, here's the important info:
The machi
Maybe I'm dense -- I thought you couldn't use --shared when linking to
a static library...?
If you want to build OMPI as a shared library, then ditch the
--enable-static --disable-shared from your configure line (building
OMPI as shared is the default, which is how I build 95% of the time).
I've been having this problem for a week or so and I've been asking
other people to weigh in if they know what I'm doing wrong. I've gotten
no where on this so I figure I'll finally drop it out on the list.
First, here's the important info:
The machine:
[sparkplug]~ > cat /etc/issue
Welcom
