Pavan Balaji, le Wed 21 Oct 2009 17:46:28 -0500, a écrit :
> Suppose you compiled hwloc with gcc, you'll get the following in your
> new config file --
>
> /* Note the hwloc_ prefix added by the AX_PREFIX_CONFIG_H macro */
> #define hwloc_restrict __restrict
>
> Now, if the application is using s
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 sp
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 space?
Not only, it's also that you never know in
> 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 space? If yes, then there are ways to avoid it while still using
AC_C_RESTRICT (see
http://www.nongnu.org/autoconf-archi
Pavan Balaji, le Wed 21 Oct 2009 13:23:39 -0500, a écrit :
> 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
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
c
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, mo
> 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
http://www.mcs.anl.gov/~ba
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
parameters,
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 suit
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. -
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?
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
c
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
> >> compiler to be C99 capable always?
> >
> > No, w
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
>> compiler to be C99 capable always?
>
> No, we ended up using constructs which should pass c90 and the compilers
> we
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
> compiler to be C99 capable always?
No, we ended up using constructs which should pass c90 and the compilers
we have tested (aix, solaris, icc).
> 2. I believe AM_CONDIT
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 t
Pavan Balaji, le Tue 20 Oct 2009 20:19:59 -0500, a écrit :
> >> 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
> > all
>> 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 app
Brice Goglin, le Tue 20 Oct 2009 23:32:38 +0200, a écrit :
> From my quick tests, if you try to build on a non-supported platform,
> you'll probably get a System object with 1 or N processors depending on
> whether sysconf is available. So building the topology looks ok. And you
> get -1 and ENOSYS
Jeff Squyres wrote:
> 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
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
cal
22 matches
Mail list logo
