The problem I see is because FreeBSD-8.2 provides a NEW autotools suite
w/ an intentionally ANCIENT config.guess.
There is nothing wrong with any of Open MPI's config.foo as packaged in
the tarball.
I can work just fine by re-extracting config.guess and config.sub from
the tarball after
I have access to several Linux platforms other than x86 and x86-64, on
which I've tested ompi-1.5.5rc1.
This info is intended to be informational, and NOT intended to
influence/delay the 1.5.5 release.
First a summary of the results, with added details below:
GOOD:
ppc32 (Apple G4 h/w): OK
I only ran autogen after I had edited a Makefile.am or a .m4 file.
-Paul
On 12/21/2011 4:58 AM, Jeff Squyres (jsquyres) wrote:
Paul -
Are you running autogen from the tarballs in your testing? You probably
shouldn't - we have users just run configure and make. We also bootstrap the
Paul -
Are you running autogen from the tarballs in your testing? You probably
shouldn't - we have users just run configure and make. We also bootstrap the
tarballs w the most recent config.sub and .guess (i.e., more recent than what
comes w the most recent Autotools).
Sent from my phone.
Paul's probably more than likely right. The nightly runs Oracle does
using MTT and tarballs do not do autogen.sh (which I believe is not
expected anyways, right). All other builds we do using autogen.* are
from an svn workspace.
--td
On 12/20/2011 8:21 PM, Paul H. Hargrove wrote:
Not too
Building openmpi-1.5.5rc1 on Solaris10/UltraSPARC-T2 (with -mcpu=v9 as
README requires) I see the following from "make check":
--> Testing atomic_cmpset
Assertion failed: volptr == newptr, file
/home/hargrove/OMPI/openmpi-1.5.5rc1//openmpi-1.5.5rc1/test/asm/atomic_cmpset.c,
line 199
When configuring hwloc-1.3.1rc1 on anything but x86 or x86-64 one sees
the following:
checking which CPU support to include... checking size of unsigned
long... 4
The patch below will change that to
checking which CPU support to include... unknown
checking size of unsigned long... 4
