I believe this has been fixed now - please let me know
> On Mar 30, 2017, at 1:57 AM, Cyril Bordage wrote:
>
> Hello,
>
> I am using the git version of MPI with "-bind-to core -report-bindings"
> and I get that for all processes:
> [miriel010:160662] MCW rank 0 not bound
>
>
> When I use an o
It hasn’t come into master - dunno if someone has it sitting on a branch
somewhere (I don’t see a PR that indicates it)
> On Apr 5, 2017, at 11:56 AM, Brice Goglin wrote:
>
> Hello
>
> Did anybody start porting OMPI to the new hwloc 2.0 API (currently in
> hwloc git master)?
> Gilles, I seem t
It could be that a fairly recent change was made to fix that conflict. I
believe Jeff and Gilles modified the internal hwloc header name(s) to ensure we
got the right one of those. However, that didn’t get done for libevent and/or
pmix, so the conflict likely still resides there.
> On Apr 5, 20
Right; that’s what I built. I had both libevent and hwloc installed in /usr.
I configured with —with-hwloc=external. It built against the external hwloc
and the internal libevent. So there must be some slight variation on the theme
I’m missing.
Brian
> On Apr 5, 2017, at 11:36 AM, r...@ope
Hello
Did anybody start porting OMPI to the new hwloc 2.0 API (currently in
hwloc git master)?
Gilles, I seem to remember you were interested a while ago?
I will have to do it in the near future. If anybody already started that
work, please let me know.
Brice
___
Not quite the problem I mentioned. The problem arises if you want external
hwloc, but internal libevent - and both have external versions in (say) /usr.
If you point hwloc there, then the -I and -L flags will cause us to pull in the
/usr libevent versions instead of the internal ones - and havoc
All -
On the telecon yesterday, there was discussion of external hwloc causing
problems if libevent was also installed in the same location. Does anyone have
details on exactly what the failure mode is? I tried what I think is the issue
(./configure —with-hwloc=external with libevent installe
