Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] EXTERNAL: Re: Unresolved reference 'mbind' and 'get_mempolicy'
From: Rayson Ho (raysonlogin_at_[hidden])
Date: 2011-12-07 17:00:09

We are using hwloc-1.2.2 for topology binding in Open Grid
Scheduler/Grid Engine 2011.11, and a user is encountering similar

In Open MPI, there is the configure switch "--without-libnuma" to turn
libnuma off. But since Open MPI uses hwloc internally, I think there
still is a dependency on libnuma even if "--without-libnuma" is used
to build Open MPI. Also, as hwloc does not have a configure switch
that disables libnuma, seems like libnuma is always used when the
hwloc configure script detects its presence.

So my question is, are there plans to add a configure switch in hwloc
to disable libnuma??


Open Grid Scheduler / Grid Engine

Scalable Grid Engine Support Program

On Fri, Sep 30, 2011 at 8:03 AM, Jeff Squyres <jsquyres_at_[hidden]> wrote:
> On Sep 29, 2011, at 12:45 PM, Blosch, Edwin L wrote:
>> If I add --without-hwloc in addition to --without-libnuma, then it builds.  Is that a reasonable thing to do?  Is there a better workaround?  This 'hwloc' module looks like it might be important.
> As a note of explanation: hwloc is effectively our replacement for libnuma.  You might want to check out hwloc (the standalone software package) -- it has a CLI and is quite useful for administrating servers, even outside of an HPC environment:
> hwloc may use libnuma under the covers; that's where this issue is coming from (i.e., OMPI may still use libnuma -- it's just now doing so indirectly, instead of directly).
>> For what it's worth, if there's something wrong with my configure line, let me know what to improve. Otherwise, as weird as "--enable-mca-no-build=maffinity --disable-io-romio --enable-static --disable-shared" may look, I am not trying to build fully static binaries. I have unavoidable need to build OpenMPI on certain machines and then transfer the executables to other machines that are compatable but not identical, and over the years these are the minimal set of configure flags necessary to make that possible. I may revisit these choices at some point, but if they are supposed to work, then I'd rather just keep using them.
> Your configure line looks fine to me.
> FWIW/heads up: in the 1.7 series, we're going to be ignoring the $F77 and $FFLAGS variables; we'll *only* be using $FC and $FCFLAGS.  There's still plenty of time before this hits mainstream, but I figured I'd let you know it's coming.  :-)
> --
> Jeff Squyres
> jsquyres_at_[hidden]
> For corporate legal information go to:
> _______________________________________________
> users mailing list
> users_at_[hidden]

Open Grid Scheduler - The Official Open Source Grid Engine