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] MPICH2 question
From: Pavan Balaji (balaji_at_[hidden])
Date: 2009-10-20 21:19:59

>> I am not sure how hard it'd be to avoid errors during configure. Are we
>> sure PKG_* macros or other external things will never use AC_MSG_ERROR ?
> In principle ac macros always have an "what if not found" part which
> allows us to fallback nicely.

Note that if you decide to take this approach, it is important that
neither the configure nor the make fail.

Alternatively, it is possible for me to build a sandbox sub-configure
within MPICH2 that'll fork/exec the hwloc configure directly and check
its exit status before deciding whether to include hwloc or not. This,
however, assumes that hwloc will either fail in configure or the library
 will be successfully built and might return an error during
initialization. But even in this case "make" should not fail.

Personally, I'd prefer the first approach, but can do with the second
approach as well.

 -- Pavan

Pavan Balaji