Le 05/09/2012 17:42, Jeff Squyres a écrit :
> On Sep 5, 2012, at 11:36 AM, Samuel Thibault wrote:
>
>>> 1. We do not allow "./configure --enable-static --enable-shared". Even
>>> though that's valid Automake/Libtool (i.e., it'll generate libhwloc.a *and*
>>> libhwloc.so), we don't allow it.
>>
Jeff Squyres, le Thu 06 Sep 2012 15:46:29 +0200, a écrit :
> On Sep 6, 2012, at 7:46 AM, Jeff Squyres wrote:
> > (sorry; I forgot to ping Shiqing yesterday -- I just did so now to get a
> > confirmation of what you found)
>
>
> Shiqing confirms that DSOs are disabled by default on Windows.
On Sep 6, 2012, at 7:46 AM, Jeff Squyres wrote:
> (sorry; I forgot to ping Shiqing yesterday -- I just did so now to get a
> confirmation of what you found)
Shiqing confirms that DSOs are disabled by default on Windows. However, he
says that they do actually work if you enable them.
--
On Sep 6, 2012, at 4:00 AM, Brice Goglin wrote:
> I just installed openmpi 1.6.1 win32.exe. I don't see any plugin in
> there. There are several libmpi*.dll or libo*.dll, but no mca_btl_* or so
Ah, ok.
(sorry; I forgot to ping Shiqing yesterday -- I just did so now to get a
confirmation of
Le 05/09/2012 18:05, Brice Goglin a écrit :
> Le 05/09/2012 17:23, Jeff Squyres a écrit :
>> On Sep 5, 2012, at 11:12 AM, Brice Goglin wrote:
>>
To be clear: we have exactly the same situation in OMPI, and we do not
link any of our DSOs against libmpi.so (we used to, but we don't any
On Sep 5, 2012, at 11:36 AM, Samuel Thibault wrote:
>> 1. We do not allow "./configure --enable-static --enable-shared". Even
>> though that's valid Automake/Libtool (i.e., it'll generate libhwloc.a *and*
>> libhwloc.so), we don't allow it.
>
> Well, actually for instance Debian builds once
On Sep 5, 2012, at 11:19 AM, Samuel Thibault wrote:
>> Undefined symbols at .so-creation time are allowed on all platforms (even OS
>> X).
>
> Even OS X? I thought I had seen such issue on OS X, precisely.
Yep.
>> But they must be resolved at load time.
>
> Or not, when resolving lazily :)
Le 05/09/2012 17:08, Jeff Squyres a écrit :
> On Sep 5, 2012, at 10:23 AM, Samuel Thibault wrote:
>
>>> The problem I was trying to fix below is that linking hwloc plugins on
>>> Darwin failed because plugins referred to hwloc-core symbols. Nothing on
>>> the libtool command-line said where to
On Sep 5, 2012, at 10:13 AM, Brice Goglin wrote:
> I understand pretty much nothing in your mails :)
Don't linkers suck? :-) That wiki page is the result of much hard-won
knowledge.
> The problem I was trying to fix below is that linking hwloc plugins on
> Darwin failed because plugins
Brice Goglin, le Wed 05 Sep 2012 16:13:31 +0200, a écrit :
> The problem I was trying to fix below is that linking hwloc plugins on
> Darwin failed because plugins referred to hwloc-core symbols. Nothing on
> the libtool command-line said where to find those symbols (I don't
> understand why it
I should clarify...
In OMPI, if we're building libmpi.so, we default to building plugins as DSOs.
If we're building libmpi.a, then we slurp all the plugins into libmpi.a (i.e.,
don't build them as DSOs). This avoids many of the issues in table 2.
On Sep 5, 2012, at 9:54 AM, Jeff Squyres
This is a bad idea.
I'm trying to remember the reason why, but we explicitly *removed* such -l
statements (e.g., removed "-lmpi" from the plugins). Hmm... Oh, right. Every
time I think I understand linkers, I find out that I don't. So last time we
had a Big Confusion Discussion About
12 matches
Mail list logo
