Re: [OMPI users] OpenMPI v3.0 on Cygwin

2017-09-27 Thread George Bosilca
On Thu, Sep 28, 2017 at 12:45 AM, Fab Tillier via users <
users@lists.open-mpi.org> wrote:

> Hi Llelan,
>
> Llelan D. wrote on Wed, 27 Sep 2017 at 19:06:23
>
> > 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
> > contracts for and associated with MS and am very familiar with their
> policy of
> > what they claim vs. what they do. Check out:
> >http://mpi-forum.org/slides/2014/11/mpi3-impl-status-Nov14.pdf
> > for where msmpi was in 2014 when they were claiming
> > the same things. The latest version of msmpi (v8.1.12438) still only
> > provides minimal support for MPI specification v2.0.
>
> Did you mean MPI 3.0 here?  We've had comprehensive support for MPI 2.0
> for quite some time, and as of version 8.1 believe we should be MPI 2.2
> compliant as well as supporting a fair bit of MPI 3.0.  We've been steadily
> adding MPI 3 support each release, and tend to prioritize development based
> on user feedback, so if there are APIs you need, please let us know - you
> can contact the MS-MPI team directly at mailto:ask...@microsoft.com.
>
> You should be able to see the evolution through the MPICH BOF slides from
> past super computing conferences.  The 2015 slides are here:
> https://www.mpich.org/files/2015/11/SC15-MPICH-BoF.pdf, but unfortunately
> the 2016 slides link is broken.
>

The link to the slides presenting the level of support of the MPI
specification by different MPI implementations can be found on the main
page of the MPI Forum at http://mpi-forum.org/ (look for Implementation
Status).

  George.


>
> > Understand, I'm no MS basher; Windows is still the most likely
> development
> > environment in the industry and must be respected. This is why I always
> > argue that it is a mistake not to distribute native MS versions of
> packages no
> > matter what level of popular support there is.
> > Allowing MS to restrict the level of support on the Windows platform to
> only
> > the avenues they wish developers to use is a huge restriction for the
> > evolution of a specification and a terrible problem for those of us who
> must
> > work cross-platform.
>
> I think you misconstrue our objectives here.  If there are APIs you would
> like us to support, let us know so that we can prioritize their
> implementation.  We also don't prevent or discourage alternative
> implementations, and while we would be more than happy to see Windows
> native Open MPI releases, we understand and respect the Open MPI
> developers' decision to invest their time elsewhere.
>
> Cheers,
> -Fab
> ___
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users
>
___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users

Re: [OMPI users] OpenMPI v3.0 on Cygwin

2017-09-27 Thread Fab Tillier via users
Hi Llelan,

Llelan D. wrote on Wed, 27 Sep 2017 at 19:06:23

> 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
> contracts for and associated with MS and am very familiar with their policy of
> what they claim vs. what they do. Check out:
>    http://mpi-forum.org/slides/2014/11/mpi3-impl-status-Nov14.pdf
> for where msmpi was in 2014 when they were claiming
> the same things. The latest version of msmpi (v8.1.12438) still only
> provides minimal support for MPI specification v2.0.

Did you mean MPI 3.0 here?  We've had comprehensive support for MPI 2.0 for 
quite some time, and as of version 8.1 believe we should be MPI 2.2 compliant 
as well as supporting a fair bit of MPI 3.0.  We've been steadily adding MPI 3 
support each release, and tend to prioritize development based on user 
feedback, so if there are APIs you need, please let us know - you can contact 
the MS-MPI team directly at mailto:ask...@microsoft.com.

You should be able to see the evolution through the MPICH BOF slides from past 
super computing conferences.  The 2015 slides are here: 
https://www.mpich.org/files/2015/11/SC15-MPICH-BoF.pdf, but unfortunately the 
2016 slides link is broken.

> Understand, I'm no MS basher; Windows is still the most likely development
> environment in the industry and must be respected. This is why I always
> argue that it is a mistake not to distribute native MS versions of packages no
> matter what level of popular support there is.
> Allowing MS to restrict the level of support on the Windows platform to only
> the avenues they wish developers to use is a huge restriction for the
> evolution of a specification and a terrible problem for those of us who must
> work cross-platform.

I think you misconstrue our objectives here.  If there are APIs you would like 
us to support, let us know so that we can prioritize their implementation.  We 
also don't prevent or discourage alternative implementations, and while we 
would be more than happy to see Windows native Open MPI releases, we understand 
and respect the Open MPI developers' decision to invest their time elsewhere.

Cheers,
-Fab
___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users

Re: [OMPI users] OpenMPI v3.0 on Cygwin

2017-09-27 Thread Llelan D.

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 
contracts for and associated with MS and am very familiar with their 
policy of what they claim vs. what they do. Check out:

  http://mpi-forum.org/slides/2014/11/mpi3-impl-status-Nov14.pdf
for where msmpi was in 2014 when they were claiming the same things. The 
latest version of msmpi (v8.1.12438) still only provides minimal support 
for MPI specification v2.0.


Understand, I'm no MS basher; Windows is still the most likely 
development environment in the industry and must be respected. This is 
why I always argue that it is a mistake not to distribute native MS 
versions of packages no matter what level of popular support there is. 
Allowing MS to restrict the level of support on the Windows platform to 
only the avenues they wish developers to use is a huge restriction for 
the evolution of a specification and a terrible problem for those of us 
who must work cross-platform.


However, my original point was about the Cygwin version of openmpi and 
not any native Windows version. Looking forward to that. :)


___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users

Re: [OMPI users] OpenMPI v3.0 on Cygwin

2017-09-27 Thread Jeffrey A Cummings
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.

- Jeff

Jeffrey A. Cummings
Engineering Specialist
Performance Modeling and Analysis Department
Systems Analysis and Simulation Subdivision
Systems Engineering Division
Engineering and Technology Group
The Aerospace Corporation
571-304-7548
jeffrey.a.cummi...@aero.org

-Original Message-
From: users [mailto:users-boun...@lists.open-mpi.org] On Behalf Of Llelan D.
Sent: Wednesday, September 27, 2017 3:22 PM
To: users@lists.open-mpi.org
Subject: Re: [OMPI users] OpenMPI v3.0 on Cygwin

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 myself. The
1.10 Cygport version compiles and packages just fine so I'll look at what was 
done to that for now and try to translate it to v3.0.

@Jeffrey A Cummings: OpenMPI has abandoned *NATIVE* windows support (*.lib for 
compilers like MSVC, etc.) and not Cygwin, though a v2.* release has been slow. 
The msmpi package has never fully supported the MPI specification (or even come 
close) and has been long (and silently) abandoned by MS as people have 
preferred other fully compliant implementations.

___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users


Re: [OMPI users] Fwd: Make All error regarding either "Conflicting" or "Previous Declaration" among others

2017-09-27 Thread Aragorn Inocencio
Good morning Jeff,

Yes, I was also watching that thread for any developments as it's pretty
much the same scenario.

On Sep 27, 2017 11:49 PM, "Jeff Squyres (jsquyres)" 
wrote:

Check out this thread on the users archive:

https://www.mail-archive.com/users@lists.open-mpi.org/msg31602.html

including Marco's reply (Marco is the Cygwin Open MPI package maintainer).


> On Sep 27, 2017, at 1:21 AM, Aragorn Inocencio <
aragorn.inocen...@gmail.com> wrote:
>
> Good afternoon guys,
>
> As instructed I have attached my log files for the configure, make, and
make install functions. Do you think there is hope for me getting this to
run in Windows via cygwin?
>
> On Fri, Sep 22, 2017 at 5:30 AM, Aragorn Inocencio <
aragorn.inocen...@gmail.com> wrote:
> Good morning,
>
> Thanks for the input Jeff; yes I am still doing this in Windows via
cygwin. I currently do not have a Linux machine.
>
> Thanks Gus, I will use those commands to build the logs. I assume I will
have to do a MAKE CLEAN before I try again right? I will try again later
tonight.
>
>
> On Sep 22, 2017 1:40 AM, "Gus Correa"  wrote:
> On 09/21/2017 11:26 AM, Aragorn Inocencio wrote:
> Hi, sorry about the mixup earlier.  But I have recently tried installing
openmpi 3.0.0 using the instructions I found in the Reef3D manual (attached
below), so
>
> ./configure CC=gcc CXX=g++ F77=gfortran FC=gfortran
--prefix=/usr/local/openmpi
>
> throws no errors, but again when I run the "make all" command next I am
getting quite a few errors, to name a few:
>
>  1. #warning "fd_set and associated macros have been defined in sys/types
>  2. error: redefinition of struct hostent
>  3. A bunch of other errors similar to 2
>  4. A bunch of errors saying, "conflicting types for 'accept' bind,
> connect etc.
>  5. "Expected declaration specifiers or '...' before '("
>  6. previous declaration of various functions
>
>
> then all the way at the end it gives me an Error 1.
>
> I'd like to apologize for my ignorance as I really have no background in
this area; I don't even know how to print all the errors to a txt file.
>
> ** If using sh/bash:
>
> ./configure CC=gcc CXX=g++ F77=gfortran FC=gfortran
--prefix=/usr/local/openmpi 2>&1 | tee my_configure.log
>
> make 2>&1 | tee my_make.log
>
> make install 2>&1 | tee my_make_install.log
>
> ** If using csh/tcsh:
>
> ./configure CC=gcc CXX=g++ F77=gfortran FC=gfortran
--prefix=/usr/local/openmpi  |& tee my_configure.log
>
> make |& tee my_make.log
>
> make install |& tee my_make_install.log
>
> I hope this helps,
> Gus Correa
>
> For what it's worth I have attached the config.log file.
>
> ​Inline image 1
>
>
>
> ___
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users
>
>
> ___
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users
>
>
>
>
> --
> Ismael Aragorn D. Inocencio
> Civil Engineer
> ___
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users


--
Jeff Squyres
jsquy...@cisco.com

___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users

Re: [OMPI users] OpenMPI v3.0 on Cygwin

2017-09-27 Thread Jeff Squyres (jsquyres)
On Sep 27, 2017, at 3:21 PM, Llelan D.  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 myself. The 1.10 
> Cygport version compiles and packages just fine so I'll look at what was done 
> to that for now and try to translate it to v3.0.

Once you guys have some patches, let's have a look at them here upstream and 
see if we can slurp them in so that you don't have to carry them forward.

What would be *awesome* is if -- assuming we get those patches slurped in 
upstream -- someone could provide some testing resources:

1. For each Github pull request
2. Nightly MTT testing (doesn't have to be too extensive)

(I'm happy to explain the details of both of these if anyone has some resources 
to volunteer -- we should probably move over to the devel list, though)

Specifically: the biggest problem we have is that no one in the Open MPI 
developer community currently develops and test on Cygwin.  Hence, if/when we 
break stuff, we don't know it until Marco has the cycles to test and then 
develop aftermarket patches.  Meaning: if we get patches to make Open MPI 
compile/work on Cygwin, those will only last until we (accidentally) break it 
again.  But if we have continual testing and integration on Cygwin (with all of 
our other CI infrastructure), that *significantly* decreases the probability of 
us breaking Cygwin again.  Or, at least, if/when we break it, we'll *know* it, 
and therefore we can *fix* it.

Make sense?

-- 
Jeff Squyres
jsquy...@cisco.com

___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users


Re: [OMPI users] OpenMPI v3.0 on Cygwin

2017-09-27 Thread Llelan D.

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 myself. The 
1.10 Cygport version compiles and packages just fine so I'll look at 
what was done to that for now and try to translate it to v3.0.


@Jeffrey A Cummings: OpenMPI has abandoned *NATIVE* windows support 
(*.lib for compilers like MSVC, etc.) and not Cygwin, though a v2.* 
release has been slow. The msmpi package has never fully supported the 
MPI specification (or even come close) and has been long (and silently) 
abandoned by MS as people have preferred other fully compliant 
implementations.


___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users


Re: [OMPI users] Fwd: Make All error regarding either "Conflicting" or "Previous Declaration" among others

2017-09-27 Thread Jeff Squyres (jsquyres)
Check out this thread on the users archive:

https://www.mail-archive.com/users@lists.open-mpi.org/msg31602.html

including Marco's reply (Marco is the Cygwin Open MPI package maintainer).


> On Sep 27, 2017, at 1:21 AM, Aragorn Inocencio  
> wrote:
> 
> Good afternoon guys,
> 
> As instructed I have attached my log files for the configure, make, and make 
> install functions. Do you think there is hope for me getting this to run in 
> Windows via cygwin?
> 
> On Fri, Sep 22, 2017 at 5:30 AM, Aragorn Inocencio 
>  wrote:
> Good morning,
> 
> Thanks for the input Jeff; yes I am still doing this in Windows via cygwin. I 
> currently do not have a Linux machine.
> 
> Thanks Gus, I will use those commands to build the logs. I assume I will have 
> to do a MAKE CLEAN before I try again right? I will try again later tonight.
> 
> 
> On Sep 22, 2017 1:40 AM, "Gus Correa"  wrote:
> On 09/21/2017 11:26 AM, Aragorn Inocencio wrote:
> Hi, sorry about the mixup earlier.  But I have recently tried installing 
> openmpi 3.0.0 using the instructions I found in the Reef3D manual (attached 
> below), so
> 
> ./configure CC=gcc CXX=g++ F77=gfortran FC=gfortran 
> --prefix=/usr/local/openmpi
> 
> throws no errors, but again when I run the "make all" command next I am 
> getting quite a few errors, to name a few:
> 
>  1. #warning "fd_set and associated macros have been defined in sys/types
>  2. error: redefinition of struct hostent
>  3. A bunch of other errors similar to 2
>  4. A bunch of errors saying, "conflicting types for 'accept' bind,
> connect etc.
>  5. "Expected declaration specifiers or '...' before '("
>  6. previous declaration of various functions
> 
> 
> then all the way at the end it gives me an Error 1.
> 
> I'd like to apologize for my ignorance as I really have no background in this 
> area; I don't even know how to print all the errors to a txt file.
> 
> ** If using sh/bash:
> 
> ./configure CC=gcc CXX=g++ F77=gfortran FC=gfortran 
> --prefix=/usr/local/openmpi 2>&1 | tee my_configure.log
> 
> make 2>&1 | tee my_make.log
> 
> make install 2>&1 | tee my_make_install.log
> 
> ** If using csh/tcsh:
> 
> ./configure CC=gcc CXX=g++ F77=gfortran FC=gfortran 
> --prefix=/usr/local/openmpi  |& tee my_configure.log
> 
> make |& tee my_make.log
> 
> make install |& tee my_make_install.log
> 
> I hope this helps,
> Gus Correa
> 
> For what it's worth I have attached the config.log file.
> 
> ​Inline image 1
> 
> 
> 
> ___
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users
> 
> 
> ___
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users
> 
> 
> 
> 
> -- 
> Ismael Aragorn D. Inocencio
> Civil Engineer
> ___
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users


-- 
Jeff Squyres
jsquy...@cisco.com

___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users

Re: [OMPI users] OpenMPI v3.0 on Cygwin

2017-09-27 Thread Jeffrey A Cummings
The OpenMPI developers stopped supporting Windows a long time (several major 
versions) ago.

Microsoft has a free version of MPI for Windows available for download.  
There's no guarantee it will be free forever but it is free for now.  I've been 
using it for about a year and it works for me.  My usage of MPI is pretty 
vanilla so there may be features missing in Microsoft's implementation.  It 
might be worth your while to at least look at it.

– Jeff

-Original Message-
From: users [mailto:users-boun...@lists.open-mpi.org] On Behalf Of Llelan D.
Sent: Wednesday, September 27, 2017 3:31 AM
To: users@lists.open-mpi.org
Subject: [OMPI users] OpenMPI v3.0 on Cygwin

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:

/usr/include/w32api/psdk_inc/_ip_types.h
 or /usr/include/w32api/winsock2.h
and/usr/include/netdb.h
 or /usr/include/sys/socket.h

Are there magic variables, definitions, or switches for a Cygwin build I'm 
missing?

___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users

Re: [OMPI users] Error building openmpi on Raspberry pi 2

2017-09-27 Thread Jeff Layton
I could never get OpenMPI < 2.x to build on a Pi 2. I ended up using the binary 
from the repos. Pi 3 is a different matter - I got that to build after a little 
experimentation :)
Jeff
 

On Wednesday, September 27, 2017 8:03 AM, Nathan Hjelm  
wrote:
 

 Open MPI does not officially support ARM in the v2.1 series. Can you download 
a nightly tarball from https://www.open-mpi.org/nightly/master/ and see if it 
works for you?

-Nathan

> On Sep 26, 2017, at 7:32 PM, Faraz Hussain  wrote:
> 
> I am receiving the make errors below on my pi 2:
> 
> pi@pi001:~/openmpi-2.1.1 $ uname -a
> Linux pi001 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
> 
> pi@pi001:~/openmpi-2.1.1 $ make -j 4
> .
> .
> .
> .
> make[2]: Entering directory '/home/pi/openmpi-2.1.1/opal/asm'
>  CPPAS    atomic-asm.lo
> atomic-asm.S: Assembler messages:
> atomic-asm.S:7: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:15: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:23: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:55: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:70: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:86: Error: selected processor does not support ARM mode `ldrexd 
> r4,r5,[r0]'
> atomic-asm.S:91: Error: selected processor does not support ARM mode `strexd 
> r1,r6,r7,[r0]'
> atomic-asm.S:107: Error: selected processor does not support ARM mode `ldrexd 
> r4,r5,[r0]'
> atomic-asm.S:112: Error: selected processor does not support ARM mode `strexd 
> r1,r6,r7,[r0]'
> atomic-asm.S:115: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:130: Error: selected processor does not support ARM mode `ldrexd 
> r4,r5,[r0]'
> atomic-asm.S:135: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:136: Error: selected processor does not support ARM mode `strexd 
> r1,r6,r7,[r0]'
> Makefile:1743: recipe for target 'atomic-asm.lo' failed
> make[2]: *** [atomic-asm.lo] Error 1
> make[2]: Leaving directory '/home/pi/openmpi-2.1.1/opal/asm'
> Makefile:2307: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/home/pi/openmpi-2.1.1/opal'
> Makefile:1806: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1
> 
> 
> ___
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users

___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users


   ___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users

Re: [OMPI users] Error building openmpi on Raspberry pi 2

2017-09-27 Thread Nathan Hjelm
Open MPI does not officially support ARM in the v2.1 series. Can you download a 
nightly tarball from https://www.open-mpi.org/nightly/master/ and see if it 
works for you?

-Nathan

> On Sep 26, 2017, at 7:32 PM, Faraz Hussain  wrote:
> 
> I am receiving the make errors below on my pi 2:
> 
> pi@pi001:~/openmpi-2.1.1 $ uname -a
> Linux pi001 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
> 
> pi@pi001:~/openmpi-2.1.1 $ make -j 4
> .
> .
> .
> .
> make[2]: Entering directory '/home/pi/openmpi-2.1.1/opal/asm'
>  CPPASatomic-asm.lo
> atomic-asm.S: Assembler messages:
> atomic-asm.S:7: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:15: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:23: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:55: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:70: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:86: Error: selected processor does not support ARM mode `ldrexd 
> r4,r5,[r0]'
> atomic-asm.S:91: Error: selected processor does not support ARM mode `strexd 
> r1,r6,r7,[r0]'
> atomic-asm.S:107: Error: selected processor does not support ARM mode `ldrexd 
> r4,r5,[r0]'
> atomic-asm.S:112: Error: selected processor does not support ARM mode `strexd 
> r1,r6,r7,[r0]'
> atomic-asm.S:115: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:130: Error: selected processor does not support ARM mode `ldrexd 
> r4,r5,[r0]'
> atomic-asm.S:135: Error: selected processor does not support ARM mode `dmb'
> atomic-asm.S:136: Error: selected processor does not support ARM mode `strexd 
> r1,r6,r7,[r0]'
> Makefile:1743: recipe for target 'atomic-asm.lo' failed
> make[2]: *** [atomic-asm.lo] Error 1
> make[2]: Leaving directory '/home/pi/openmpi-2.1.1/opal/asm'
> Makefile:2307: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/home/pi/openmpi-2.1.1/opal'
> Makefile:1806: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1
> 
> 
> ___
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users

___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users


Re: [OMPI users] OpenMPI v3.0 on Cygwin

2017-09-27 Thread Marco Atzeri

On 27/09/2017 09:30, Llelan D. wrote:

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:

    /usr/include/w32api/psdk_inc/_ip_types.h
     or /usr/include/w32api/winsock2.h
and    /usr/include/netdb.h
     or /usr/include/sys/socket.h

Are there magic variables, definitions, or switches for a Cygwin build 
I'm missing?




Hi Llelan,
I assume no, and expect it needs some patches as I am slowing
doing for 2.1.2.
There are portion of the code that rise definitions that collides
with the Windows headers for not Cygwin programs.

After I finish on 2.1.2 I will look on 3.0.

Regards
Marco



___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users

[OMPI users] OpenMPI v3.0 on Cygwin

2017-09-27 Thread Llelan D.

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:

   /usr/include/w32api/psdk_inc/_ip_types.h
or /usr/include/w32api/winsock2.h
and/usr/include/netdb.h
    or /usr/include/sys/socket.h

Are there magic variables, definitions, or switches for a Cygwin build 
I'm missing?


___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users

Re: [OMPI users] Error building openmpi on Raspberry pi 2

2017-09-27 Thread John Hearns via users
This might be of interest for ARM users:
https://developer.arm.com/products/software-development-tools/hpc/arm-compiler-for-hpc



On 27 September 2017 at 06:58, Gilles Gouaillardet <
gilles.gouaillar...@gmail.com> wrote:

> Faraz,
>
> which OS are you running ?
>
> iirc, i faced similar issues, and the root cause is that though ARMv7
> does support these instructions, the compiler only generate ARMv6 code
> and hence failed to build Open MPI
>
> Cheers,
>
> Gilles
>
> On Wed, Sep 27, 2017 at 10:32 AM, Faraz Hussain 
> wrote:
> > I am receiving the make errors below on my pi 2:
> >
> > pi@pi001:~/openmpi-2.1.1 $ uname -a
> > Linux pi001 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l
> > GNU/Linux
> >
> > pi@pi001:~/openmpi-2.1.1 $ make -j 4
> > .
> > .
> > .
> > .
> > make[2]: Entering directory '/home/pi/openmpi-2.1.1/opal/asm'
> >   CPPASatomic-asm.lo
> > atomic-asm.S: Assembler messages:
> > atomic-asm.S:7: Error: selected processor does not support ARM mode `dmb'
> > atomic-asm.S:15: Error: selected processor does not support ARM mode
> `dmb'
> > atomic-asm.S:23: Error: selected processor does not support ARM mode
> `dmb'
> > atomic-asm.S:55: Error: selected processor does not support ARM mode
> `dmb'
> > atomic-asm.S:70: Error: selected processor does not support ARM mode
> `dmb'
> > atomic-asm.S:86: Error: selected processor does not support ARM mode
> `ldrexd
> > r4,r5,[r0]'
> > atomic-asm.S:91: Error: selected processor does not support ARM mode
> `strexd
> > r1,r6,r7,[r0]'
> > atomic-asm.S:107: Error: selected processor does not support ARM mode
> > `ldrexd r4,r5,[r0]'
> > atomic-asm.S:112: Error: selected processor does not support ARM mode
> > `strexd r1,r6,r7,[r0]'
> > atomic-asm.S:115: Error: selected processor does not support ARM mode
> `dmb'
> > atomic-asm.S:130: Error: selected processor does not support ARM mode
> > `ldrexd r4,r5,[r0]'
> > atomic-asm.S:135: Error: selected processor does not support ARM mode
> `dmb'
> > atomic-asm.S:136: Error: selected processor does not support ARM mode
> > `strexd r1,r6,r7,[r0]'
> > Makefile:1743: recipe for target 'atomic-asm.lo' failed
> > make[2]: *** [atomic-asm.lo] Error 1
> > make[2]: Leaving directory '/home/pi/openmpi-2.1.1/opal/asm'
> > Makefile:2307: recipe for target 'all-recursive' failed
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory '/home/pi/openmpi-2.1.1/opal'
> > Makefile:1806: recipe for target 'all-recursive' failed
> > make: *** [all-recursive] Error 1
> >
> >
> > ___
> > users mailing list
> > users@lists.open-mpi.org
> > https://lists.open-mpi.org/mailman/listinfo/users
> ___
> users mailing list
> users@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/users
>
___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users