Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

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.

Subject: Re: [hwloc-devel] Embedding: is it worth it?
From: Samuel Thibault (samuel.thibault_at_[hidden])
Date: 2010-04-04 12:15:37

Jeff Squyres, le Fri 02 Apr 2010 14:51:06 -0400, a écrit :
> On Apr 2, 2010, at 2:25 PM, Samuel Thibault wrote:
> > > But to use an external PLPA/libltdl/whatever, OMPI's configure would just call their configure
> >
> > I'm not 100% sure what RedHat etc. do, but in Debian the policy wouldn't
> > be to do this, but to just link against the existing installed library,
> > i.e. use the installed hwloc.pc file only, _not_ run its configure
> > script. I believe that's what RedHat etc. mean.
> Yes.
> To be clear, if OMPI is to use the internal/embedded copy, it would just call the $path_to_hwloc/configure.

Do you mean that if OMPI had to be able to use an external copy in some
cases, for the internal case it would now just use ./configure? Why
is it so? Can't the main ./configure call the hwloc m4 stuff or not
depending on whether the internal or the external version is used?