Re: [hwloc-devel] MPICH2 question

2009-10-21 Thread Pavan Balaji
On 10/21/2009 04:44 PM, Samuel Thibault wrote: > Pavan Balaji, le Wed 21 Oct 2009 16:40:42 -0500, a écrit : >>> Please read this thread: >>> >>> http://www.open-mpi.org/community/lists/hwloc-devel/2009/09/0054.php >> Thanks. Is the only issue to not use AC_C_RESTRICT that of conflicting >> name

Re: [hwloc-devel] MPICH2 question

2009-10-21 Thread Pavan Balaji
On 10/21/2009 10:38 AM, Samuel Thibault wrote: > Pavan Balaji, le Wed 21 Oct 2009 10:36:33 -0500, a écrit : >> On 10/21/2009 10:28 AM, Samuel Thibault wrote: >>> Pavan Balaji, le Wed 21 Oct 2009 09:55:36 -0500, a écrit : 1. I see a AC_PROG_CC_C99 in the configure.ac. Do you require the

Re: [hwloc-devel] MPICH2 question

2009-10-21 Thread Jeff Squyres
On Oct 21, 2009, at 1:18 PM, Samuel Thibault wrote: > configuring/building hwloc with icc results in a *lot* > of warnings; I didn't test functionality). Mmm, I have already successfully tested with icc9. The kind of warnings I've seen were not worth fixing to my mind: unused parameters,

Re: [hwloc-devel] MPICH2 question

2009-10-21 Thread Pavan Balaji
> Pavan -- is it a problem to always compile hwloc with gcc? Yeah, this will be a problem. For us to enable hwloc by default, it'll need to build with all compilers and on all platforms without errors (and hopefully without warnings either). -- Pavan -- Pavan Balaji

Re: [hwloc-devel] MPICH2 question

2009-10-21 Thread Samuel Thibault
Jeff Squyres, le Wed 21 Oct 2009 12:50:55 -0400, a écrit : > configuring/building hwloc with icc results in a *lot* > of warnings; I didn't test functionality). Mmm, I have already successfully tested with icc9. The kind of warnings I've seen were not worth fixing to my mind: unused

Re: [hwloc-devel] MPICH2 question

2009-10-21 Thread Samuel Thibault
Jeff Squyres, le Wed 21 Oct 2009 12:46:38 -0400, a écrit : > I'd be surprised if there's a system out there that doesn't have some > flavor of egrep that satisfies AC_PROG_EGREP (especially if Libtool > uses it heavily). Do we know if this is the case, or is this a > hypothetical that a

Re: [hwloc-devel] MPICH2 question

2009-10-21 Thread Jeff Squyres
FWIW, I see at least some GNU-isms in the hwloc code that might be problematic for embedding hwloc in other code bases that don't use gcc to compile. E.g., in OMPI, we'd prefer to use the same compiler suite to compile hwloc that was used to compile OMPI itself (e.g., intel, PGI, ...etc.

Re: [hwloc-devel] MPICH2 question

2009-10-21 Thread Jeff Squyres
On Oct 21, 2009, at 10:20 AM, Samuel Thibault wrote: I've checked configure, only the check for egrep may fail and does not provide any fallback which we could have used. It's only used for the documentation generation, Jeff, maybe we can find an alternative to egrep for what we use it for?

Re: [hwloc-devel] MPICH2 question

2009-10-21 Thread Pavan Balaji
On 10/21/2009 10:38 AM, Samuel Thibault wrote: > Pavan Balaji, le Wed 21 Oct 2009 10:36:33 -0500, a écrit : >> On 10/21/2009 10:28 AM, Samuel Thibault wrote: >>> Pavan Balaji, le Wed 21 Oct 2009 09:55:36 -0500, a écrit : 1. I see a AC_PROG_CC_C99 in the configure.ac. Do you require the

[hwloc-devel] MPICH2 question

2009-10-20 Thread Jeff Squyres
Pavan and I chatted on the phone this morning about https://svn.open-mpi.org/trac/hwloc/ticket/4 . The *easiest* solution for MPICH2 would be if they could AC_CONFIG_SUBDIRS our configure script. However, this has the condition that hwloc's configure could never fail -- e.g., it can't