Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.1a1r2492
Start time: Thu Sep 23 21:01:05 EDT 2010
End time: Thu Sep 23 21:03:11 EDT 2010
Your friendly daemon,
Cyrador
We can build an SVN checkout, but with a tarball we get this:
...
Undefined first referenced
symbol in file
opal_backtrace_print../../../opal/.libs/libopen-pal.so
opal_backtrace_buffer
* Jeff Squyres wrote on Thu, Sep 23, 2010 at 08:11:41PM CEST:
> On Sep 23, 2010, at 2:03 PM, Ralf Wildenhues wrote:
>
> >> Is the call to AM_SILENT_RULES now moot because it's listed in
> >> AM_INIT_AUTOMAKE?
> >
> > Oh, just drop that hunk, that was leftover junk in my tree and isn't
> >
On Sep 23, 2010, at 2:03 PM, Ralf Wildenhues wrote:
>> Is the call to AM_SILENT_RULES now moot because it's listed in
>> AM_INIT_AUTOMAKE?
>
> Oh, just drop that hunk, that was leftover junk in my tree and isn't
> really needed any more; I didn't mean to send it along.
Is the silent-rules
Hi Jeff,
* Jeff Squyres wrote on Thu, Sep 23, 2010 at 03:31:32PM CEST:
> One very minor question: I notice you added silent-rules to
> AM_INIT_AUTOMAKE (and bumped the required version, too), but still
> left in the call to AM_SILENT_RULES:
>
> -AM_INIT_AUTOMAKE([foreign dist-bzip2
On Sep 23, 2010, at 12:25 PM, Barrett, Brian W wrote:
> I unfortunately don't have many cycles to think about this before Oct 1, but
> I'm still a little concerned about the portability aspects of having hwloc be
> a first class citizen of OMPI - if we support a platform hwloc doesn't, that
>
On Sep 22, 2010, at 21:08 , Jeff Squyres wrote:
> WHAT: Make hwloc a 1st class item in OMPI
>
> WHY: At least 2 pieces of new functionality want/need to use the hwloc data
>
> WHERE: Put it in ompi/hwloc
>
> WHEN: Some time in the 1.5 series
>
> TIMEOUT: Tues teleconf, Oct 5 (about 2 weeks
I unfortunately don't have many cycles to think about this before Oct 1, but
I'm still a little concerned about the portability aspects of having hwloc be a
first class citizen of OMPI - if we support a platform hwloc doesn't, that
seems like it will still cause problems...
Brian
On Sep 22,
Hello OpenMPI developers,
just-released Autoconf 2.68 contains more stringent checks and warnings
about stuff passed to AC_{COMPILE,LINK,RUN}_IFELSE and AC_TRY_* macros.
Specifically, it will warn if C or C++ programs are not generated with
AC_LANG_SOURCE or AC_LANG_PROGRAM, in order to avoid
