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.
What are you trying to do with lt_dlopen? It seems like you should always
go through the MCA base utilities. If one's missing, adding it there
seems like the right mechanism.
On Wed, 29 Jul 2009, Josh Hursey wrote:
> George suggested that to me as well yesterday after the meeting. So we would
> create opal interfaces to libtool (similar to what we do with the event
> engine). That might be the best way to approach this.
> I'll start to take a look at implementing this. Since opal/libltdl is not
> part of the repository, is there a 'right' place to put this header? maybe in
> On Jul 28, 2009, at 6:57 PM, Jeff Squyres (jsquyres) wrote:
>> Josh - this is almost certainly what happened. Yoibks. Unfortunately,
>> there's good reasons for it. :(
>> What about if we proxy calls to lt_dlopen through an opal function call?
>> Sent from my PDA. No type good.
>> ----- Original Message -----
>> From: devel-bounces_at_[hidden] <devel-bounces_at_[hidden]>
>> To: Open MPI Developers <devel_at_[hidden]>
>> Sent: Tue Jul 28 16:39:42 2009
>> Subject: Re: [OMPI devel] libtool issue with crs/self
>> It was mentioned to me that r21731 might have caused this problem by
>> restricting the visibility of the libltdl library.
>> Do you have any thoughts on how we might extend the visibility so that
>> MCA components could also use the libtool in opal?
>> I can try to initialize libtool in the Self CRS component and use it
>> directly, but since it is already opened by OPAL, I think it might be
>> better to use the instantiation in OPAL.
>> On Jul 28, 2009, at 3:06 PM, Josh Hursey wrote:
>>> Once upon a time, the Self CRS module worked correctly, but I admit
>>> that I have not tested it in a long time.
>>> The Self CRS component uses dl_open and friends to inspect the
>>> running process for a particular set of functions. When I try to run
>>> an MPI program that contains these signatures I get the following
>>> error when it tries to resolve lt_dlopen() in
>>> my-app: symbol lookup error: /path/to/install/lib/openmpi/
>>> mca_crs_self.so: undefined symbol: lt_dlopen
>>> I am configuring with the following:
>>> ./configure --prefix=/path/to/install \
>>> --enable-binaries \
>>> --with-devel-headers \
>>> --enable-debug \
>>> --enable-mpi-threads \
>>> --with-ft=cr \
>>> --without-memory-manager \
>>> --enable-ft-thread \
>>> CC=gcc CXX=g++ \
>>> F77=gfortran FC=gfortran
>>> The source code is at the link below:
>>> Does anyone have any thoughts on what might be going wrong here?
>>> devel mailing list
>> devel mailing list
>> devel mailing list
> devel mailing list