On Apr 21, 2006, at 3:26 AM, Alexander Spiegel wrote:
I'm trying to compile OpenMPI 1.0.2 on a Sparc/Solaris machine
with Sun Studio 11 compilers in 64 bit addressing mode.
t@1 (l@1) signal BUS (invalid address alignment) in
mca_allocator_bucket_alloc_align at line 206 in file
"allocator_bu
I miss that part of the MPI 2 errata. I made the corrections, now
MPI_LONG_LONG and MPI_LONG_LONG_INT are identical. Therefore one will
have MPI_LONG_LONG == MPI_LONG_LONG_INT.
You can use it from the trunk starting from revision 9701. It will be
back-ported on the 1.1 and 1.0.3 on the next
> -Original Message-
> From: users-boun...@open-mpi.org
> [mailto:users-boun...@open-mpi.org] On Behalf Of
> laurent.po...@fr.thalesgroup.com
> Sent: Friday, April 21, 2006 4:54 AM
> To: us...@open-mpi.org
> Subject: Re: [OMPI users] users Digest, Vol 261, Issue 4
>
> > That being said,
Hi,
The current and the previous versions of OpenMPI define MPI_LONG_LONG_INT and
MPI_LONG_LONG constants as the address of two distinct global variables
(&ompi_mpi_long_long_int and &ompi_mpi_long_long respectively) which makes the
following expression true: MPI_LONG_LONG_INT != MPI_LONG_LONG
Brain
sorry i am enclosing my config.log file tar file here
I can not reach to make step
Hence can not include it
config.log.bz2
Description: Binary data
config.out
Description: Binary data
On Mon, 24 Apr 2006, Galen Mark Shipman wrote:
Hi Galen,
I face this problem with releases 1.0.1 and 1.0.2. It probably isn't an
issue with Open MPI as there have been instances earlier where setting
mpi_leave_pinned to 1 didn't throw up errors. I suspect it is an issue
with the compute nodes but
Hi Aniruddha,
Are you using the trunk, or one of the release tar files (if so which one).
I will try to reproduce this as time permits but I am out of town so
please expect some delay.
Thanks,
Galen
> Hi,
>
> I keep getting a vapi error when running any NAS benchmark on Infiniband
> with mpi_
