On Apr 4, 2010, at 12:15 PM, Samuel Thibault wrote: > > 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?
Yes. > 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? No -- we wouldn't want to call the m4 stuff in the external case, because what if it came to different answers vs. how the external one is configured? (e.g., if OMPI is built using icc and the external copy was built with gcc) In the external case, OMPI should just use the external's hwloc.h and whatever decisions were already made there (sizes, types, etc.). Make sense? -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
