On 09/27/2017 3:04 PM, Jeffrey A Cummings wrote:
The MS-MPI developers disagree with your statement below and claim to be
actively working on MPI-3.0 compliance, with an expected new version release
about every six month.
They can disagree as much as they want. I've spent over 30 years doing
On 09/27/2017 4:36 AM, Marco Atzeri wrote:
After I finish on 2.1.2 I will look on 3.0.
Thank you for your response. I am looking forward to a Cygwin release.
If you could send me some guidelines as to the preferred manner of doing
this as was done with previous versions, I could work on it
Can OpenMPI v3.0 be compiled for Cygwin64 on Windows 10?
Using:
./congifure --prefix=/usr/local
[blah, blah... Apparently successful (At least it doesn't say there's an
error)]
make -j 12 all
I'm getting a slew of compiler errors about redefinitions between:
On 09/08/2017 8:16 AM, Marco Atzeri wrote:
please reply in the mailing list
Oops! My apologies. I'm not used to a mailing list without the reply-to
set to the mailing list.
Can a version of open mpi be built using x86_64-w64-mingw32-gcc so
that it will work with code compiled with
Windows 10 64bit, Cygwin64, openmpi 1.10.7-1 (dev, c, c++,
fortran), x86_64-w64-mingw32-gcc 6.3.0-1 (core, gcc, g++, fortran)
I am compiling the standard "hello_c.c" example with mgicc
configured to use the Cygwin installed MinGW gcc compiler:
$ export
Windows 10 64bit, Cygwin64, openmpi 1.10.7-1 (dev, c, c++,
fortran), GCC 6.3.0-2 (core, gcc, g++, fortran)
I am compiling the standard "hello_c.c" example with mgicc:
$ mpicc -g hello_c.c -o hello_c
The showme:
gcc -g hello_c.c -o hello_c -fexceptions -L/usr/lib
