Open MPI User's Mailing List Archives

Subject: Re: [OMPI users] openmpi-1.6 undefined reference
From: marco atzeri (marco.atzeri_at_[hidden])
Date: 2012-05-24 00:33:02

• Next message: Shiqing Fan: "Re: [OMPI users] ***UNCHECKED*** OpenMPI build configure error on Windows 7 / MinGW"
• Previous message: Jonathan Dursi: "Re: [OMPI users] possible bug exercised by mpi4py"
• In reply to: Jeff Squyres: "Re: [OMPI users] openmpi-1.6 undefined reference"
• Next in thread: devendra rai: "[OMPI users] How does OpenMPI's progress engine determine progress?"

On 5/24/2012 2:51 AM, Jeff Squyres wrote:
> On May 23, 2012, at 6:20 PM, marco atzeri wrote:
>
>> ~ 90% of the time we have mismatch problems between upstream and
>> cygwin on autoconf/automake/libtool versions that are not cygwin
>> aware or updated.
>
> Ok, fair enough.
>
> I'd be curious if you actually need to do this with Open MPI --
> we use very recent versions of the GNU Autotools to bootstrap our
> tarballs.
>

Just tested without autogen, no difference.

Cheers
Marco

• Next message: Shiqing Fan: "Re: [OMPI users] ***UNCHECKED*** OpenMPI build configure error on Windows 7 / MinGW"
• Previous message: Jonathan Dursi: "Re: [OMPI users] possible bug exercised by mpi4py"
• In reply to: Jeff Squyres: "Re: [OMPI users] openmpi-1.6 undefined reference"
• Next in thread: devendra rai: "[OMPI users] How does OpenMPI's progress engine determine progress?"