date:20150609

Re: [OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

2015-06-09 Thread Jeff Squyres (jsquyres)

Siegmar --

I don't see any reason why this should be happening to you only sometimes; this 
code has been unchanged in *forever*.  :-(

Did your NFS server drift out of time sync with your build machine, perchance?

Regardless, I just pushed what should be a workaround to master and I'll PR it 
over to v1.8 and v1.10 (it'll take a day or so for these to show up in the 
nightly tarballs) -- it should avoid the issue altogether.



> On Jun 9, 2015, at 6:44 AM, Siegmar Gross 
>  wrote:
> 
> Hi,
> 
> today I tried to build openmpi-v1.8.5-46-g9f5f498 on my machines
> (Solaris 10 Sparc, Solaris 10 x86_64, and openSUSE Linux 12.1
> x86_64) with gcc-4.9.2 and Sun C 5.13 and I got the same error
> on all three platforms with both compilers. I have already
> reported the problem a few days ago. I used the following command
> to configure the package.
> 
> ../openmpi-v1.8.5-46-g9f5f498/configure \
>  --prefix=/usr/local/openmpi-1.8.6_64_gcc \
>  --libdir=/usr/local/openmpi-1.8.6_64_gcc/lib64 \
>  --with-jdk-bindir=/usr/local/jdk1.8.0/bin \
>  --with-jdk-headers=/usr/local/jdk1.8.0/include \
>  JAVA_HOME=/usr/local/jdk1.8.0 \
>  LDFLAGS="-m64" CC="gcc" CXX="g++" FC="gfortran" \
>  CFLAGS="-m64" CXXFLAGS="-m64" FCFLAGS="-m64" \
>  CPP="cpp" CXXCPP="cpp" \
>  CPPFLAGS="" CXXCPPFLAGS="" \
>  --enable-mpi-cxx \
>  --enable-cxx-exceptions \
>  --enable-mpi-java \
>  --enable-heterogeneous \
>  --enable-mpi-thread-multiple \
>  --with-threads=posix \
>  --with-hwloc=internal \
>  --without-verbs \
>  --with-wrapper-cflags="-std=c11 -m64" \
>  --with-wrapper-cxxflags="-m64" \
>  --with-wrapper-fcflags="-m64" \
>  --enable-debug \
>  |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc
> 
> 
> ...
> make[3]: Entering directory 
> `/export2/src/openmpi-1.8.6/openmpi-1.8.6-Linux.x86_64.64_gcc/ompi/include'
> ../../../openmpi-v1.8.5-46-g9f5f498/ompi/mpi/fortran/base/gen-mpi-sizeof.pl \
>--header=mpif-sizeof.h --ierror=mandatory \
>--maxrank=7 \
>--generate=1 \
>--real16=1 \
>--complex32=1
> ln -s 
> ../../../openmpi-v1.8.5-46-g9f5f498/opal/include/opal/opal_portable_platform.h
>  mpi_portable_platform.h
> ln: failed to create symbolic link `mpi_portable_platform.h': File exists
> make[3]: *** [mpi_portable_platform.h] Error 1
> make[3]: Leaving directory 
> `/export2/src/openmpi-1.8.6/openmpi-1.8.6-Linux.x86_64.64_gcc/ompi/include'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory 
> `/export2/src/openmpi-1.8.6/openmpi-1.8.6-Linux.x86_64.64_gcc/ompi/include'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory 
> `/export2/src/openmpi-1.8.6/openmpi-1.8.6-Linux.x86_64.64_gcc/ompi'
> make: *** [all-recursive] Error 1
> linpc1 openmpi-1.8.6-Linux.x86_64.64_gcc 261 
> 
> 
> I would be grateful, if somebody could fix the problem. Thank
> you very much for any help in advance.
> 
> 
> Kind regards
> 
> Siegmar
> 
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/06/27057.php


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

2015-06-09 Thread Gilles Gouaillardet


Jeff,

Raspbian is built for armv6
(unlike linaro which is built for armv7)

that being said, you are running on an armv7 cpu, so i am not sure 
"cross-compiling"
is appropriate. (e.g. if you run a 32 bits gcc binary on an x86_64 os to 
build a x86_64 binary,

is this called cross compilation ?)

my guess is raspbian gcc 4.6 is not able to compile for armv7, even with 
some extra flags.


can you try
sudo apt-get install gcc-4.8 g++-4.8
and configure with CC=gcc48 CXX=g++48
(or whatever the gcc 4.8 compiler name is)

if that works, i will think of updating configure so it fails with an 
understandable error message

when building for armv6

Cheers,

Gilles

On 6/10/2015 2:18 AM, Jeff Layton wrote:

Gilles,

I was looking in Raspbian a little and do you know what I found?
When I do "gcc -v" it says it was built with "--with-arch=armv6".
Since I'm trying to compile on a Pi 2, doesn't this mean I'm
cross-compiling?

Thanks!

Jeff


Jeff,

btw, did you try a pI 1 before a pi2 ?

I checked some forums, and you will likely have to upgrade gcc to 4.8

a simpler option could be linaro 
https://www.raspberrypi.org/forums/viewtopic.php?f=56=98997


Cheers,

Gilles

On Tuesday, June 9, 2015, Gilles Gouaillardet 
> wrote:


Jeff,

can you
gcc -march=armv7-a foo.c

Cheers,

Gilles

On Tuesday, June 9, 2015, Jeff Layton > wrote:

Gilles,

I'm not cross-compiling - I'm building on the Pi 2.

I'm not sure how to check if gcc can generate armv7 code.
I'm using Raspbian and I'm just using the default compilers
that come with it (I think it's gcc 4.6.3).

Thanks!

Jeff

Jeff,

dmb is available only on ARMv7 (Pi 2)

if i remember correctly, you are building Open MPI on
ARMv7 as well (Pi 2),
so this is not a cross compilation issue.

if you configure with -march=armv7, the relevant log is
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I.
-I../../opal/include -I../../orte/include
-I../../ompi/include -I../../oshmem/include
-I../../opal/mca/hwloc/hwloc191/hwloc/include/private/autogen
-I../../opal/mca/hwloc/hwloc191/hwloc/include/hwloc/autogen
-I../..
-I/work/pi/src/openmpi-1.8.5/opal/mca/hwloc/hwloc191/hwloc/include
-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent

-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent/include
-march=armv7 -MT atomic-asm.lo -MD -MP -MF
.deps/atomic-asm.Tpo -c atomic-asm.S  -fPIC -DPIC -o
.libs/atomic-asm.o^M
atomic-asm.S:1:0: error: target CPU does not support ARM mode

which is very puzzling ...

can you confirm
1) you are not cross compiling
2) your gcc can generate code for armv7 ?

Cheers,

Gilles




On 6/9/2015 1:48 AM, Jeff Layton wrote:

Jeff,

Sorry - I was traveling for a week and didn't have to
the RPi.

What happens if you don't supply CCASFLAGS at all?


The output from "make" is below. It died when it
tried to compile
atomic-local. It says the processor doesn't support
ARM mode "dmb".

Thanks!

Jeff



pi@raspberrypi /work/pi/src/openmpi-1.8.5 $ make
Making all in config
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/config'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory
'/work/pi/src/openmpi-1.8.5/config'
Making all in contrib
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/contrib'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory
'/work/pi/src/openmpi-1.8.5/contrib'
Making all in opal
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal'
Making all in include
make[2]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make  all-am
make[3]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make[3]: Leaving directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make[2]: Leaving directory
'/work/pi/src/openmpi-1.8.5/opal/include'
Making all in asm
make[2]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/asm'

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

2015-06-09 Thread Jeff Layton


Gilles,

I was looking in Raspbian a little and do you know what I found?
When I do "gcc -v" it says it was built with "--with-arch=armv6".
Since I'm trying to compile on a Pi 2, doesn't this mean I'm
cross-compiling?

Thanks!

Jeff


Jeff,

btw, did you try a pI 1 before a pi2 ?

I checked some forums, and you will likely have to upgrade gcc to 4.8

a simpler option could be linaro 
https://www.raspberrypi.org/forums/viewtopic.php?f=56=98997


Cheers,

Gilles

On Tuesday, June 9, 2015, Gilles Gouaillardet 
> 
wrote:


Jeff,

can you
gcc -march=armv7-a foo.c

Cheers,

Gilles

On Tuesday, June 9, 2015, Jeff Layton > wrote:

Gilles,

I'm not cross-compiling - I'm building on the Pi 2.

I'm not sure how to check if gcc can generate armv7 code.
I'm using Raspbian and I'm just using the default compilers
that come with it (I think it's gcc 4.6.3).

Thanks!

Jeff

Jeff,

dmb is available only on ARMv7 (Pi 2)

if i remember correctly, you are building Open MPI on
ARMv7 as well (Pi 2),
so this is not a cross compilation issue.

if you configure with -march=armv7, the relevant log is
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I.
-I../../opal/include -I../../orte/include
-I../../ompi/include -I../../oshmem/include
-I../../opal/mca/hwloc/hwloc191/hwloc/include/private/autogen
-I../../opal/mca/hwloc/hwloc191/hwloc/include/hwloc/autogen -I../..
-I/work/pi/src/openmpi-1.8.5/opal/mca/hwloc/hwloc191/hwloc/include
-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent

-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent/include
-march=armv7 -MT atomic-asm.lo -MD -MP -MF
.deps/atomic-asm.Tpo -c atomic-asm.S  -fPIC -DPIC -o
.libs/atomic-asm.o^M
atomic-asm.S:1:0: error: target CPU does not support ARM mode

which is very puzzling ...

can you confirm
1) you are not cross compiling
2) your gcc can generate code for armv7 ?

Cheers,

Gilles




On 6/9/2015 1:48 AM, Jeff Layton wrote:

Jeff,

Sorry - I was traveling for a week and didn't have to
the RPi.

What happens if you don't supply CCASFLAGS at all?


The output from "make" is below. It died when it tried
to compile
atomic-local. It says the processor doesn't support
ARM mode "dmb".

Thanks!

Jeff



pi@raspberrypi /work/pi/src/openmpi-1.8.5 $ make
Making all in config
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/config'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory
'/work/pi/src/openmpi-1.8.5/config'
Making all in contrib
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/contrib'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory
'/work/pi/src/openmpi-1.8.5/contrib'
Making all in opal
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal'
Making all in include
make[2]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make  all-am
make[3]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make[3]: Leaving directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make[2]: Leaving directory
'/work/pi/src/openmpi-1.8.5/opal/include'
Making all in asm
make[2]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/asm'
  CC   asm.lo
rm -f atomic-asm.S
ln -s "../../opal/asm/generated/atomic-local.s"
atomic-asm.S
  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

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

2015-06-09 Thread Jeff Layton


Gilles,

Let me know if you think I should upgrade to gcc-4.8 and I'll
try it.

Thanks!

Jeff



Jeff,

btw, did you try a pI 1 before a pi2 ?

I checked some forums, and you will likely have to upgrade gcc to 4.8

a simpler option could be linaro 
https://www.raspberrypi.org/forums/viewtopic.php?f=56=98997


Cheers,

Gilles

On Tuesday, June 9, 2015, Gilles Gouaillardet 
> 
wrote:


Jeff,

can you
gcc -march=armv7-a foo.c

Cheers,

Gilles

On Tuesday, June 9, 2015, Jeff Layton > wrote:

Gilles,

I'm not cross-compiling - I'm building on the Pi 2.

I'm not sure how to check if gcc can generate armv7 code.
I'm using Raspbian and I'm just using the default compilers
that come with it (I think it's gcc 4.6.3).

Thanks!

Jeff

Jeff,

dmb is available only on ARMv7 (Pi 2)

if i remember correctly, you are building Open MPI on
ARMv7 as well (Pi 2),
so this is not a cross compilation issue.

if you configure with -march=armv7, the relevant log is
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I.
-I../../opal/include -I../../orte/include
-I../../ompi/include -I../../oshmem/include
-I../../opal/mca/hwloc/hwloc191/hwloc/include/private/autogen
-I../../opal/mca/hwloc/hwloc191/hwloc/include/hwloc/autogen -I../..
-I/work/pi/src/openmpi-1.8.5/opal/mca/hwloc/hwloc191/hwloc/include
-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent

-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent/include
-march=armv7 -MT atomic-asm.lo -MD -MP -MF
.deps/atomic-asm.Tpo -c atomic-asm.S  -fPIC -DPIC -o
.libs/atomic-asm.o^M
atomic-asm.S:1:0: error: target CPU does not support ARM mode

which is very puzzling ...

can you confirm
1) you are not cross compiling
2) your gcc can generate code for armv7 ?

Cheers,

Gilles




On 6/9/2015 1:48 AM, Jeff Layton wrote:

Jeff,

Sorry - I was traveling for a week and didn't have to
the RPi.

What happens if you don't supply CCASFLAGS at all?


The output from "make" is below. It died when it tried
to compile
atomic-local. It says the processor doesn't support
ARM mode "dmb".

Thanks!

Jeff



pi@raspberrypi /work/pi/src/openmpi-1.8.5 $ make
Making all in config
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/config'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory
'/work/pi/src/openmpi-1.8.5/config'
Making all in contrib
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/contrib'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory
'/work/pi/src/openmpi-1.8.5/contrib'
Making all in opal
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal'
Making all in include
make[2]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make  all-am
make[3]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make[3]: Leaving directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make[2]: Leaving directory
'/work/pi/src/openmpi-1.8.5/opal/include'
Making all in asm
make[2]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/asm'
  CC   asm.lo
rm -f atomic-asm.S
ln -s "../../opal/asm/generated/atomic-local.s"
atomic-asm.S
  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

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

2015-06-09 Thread Jeff Layton


Gilles,

No I didn't. This is a fresh Raspbian for the Pi 2. I'm using the
05-05-raspbian-wheezy image, plus I did ant apt-get update
about a week ago.

Thanks!

Jeff


Jeff,

btw, did you try a pI 1 before a pi2 ?

I checked some forums, and you will likely have to upgrade gcc to 4.8

a simpler option could be linaro 
https://www.raspberrypi.org/forums/viewtopic.php?f=56=98997


Cheers,

Gilles

On Tuesday, June 9, 2015, Gilles Gouaillardet 
> 
wrote:


Jeff,

can you
gcc -march=armv7-a foo.c

Cheers,

Gilles

On Tuesday, June 9, 2015, Jeff Layton > wrote:

Gilles,

I'm not cross-compiling - I'm building on the Pi 2.

I'm not sure how to check if gcc can generate armv7 code.
I'm using Raspbian and I'm just using the default compilers
that come with it (I think it's gcc 4.6.3).

Thanks!

Jeff

Jeff,

dmb is available only on ARMv7 (Pi 2)

if i remember correctly, you are building Open MPI on
ARMv7 as well (Pi 2),
so this is not a cross compilation issue.

if you configure with -march=armv7, the relevant log is
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I.
-I../../opal/include -I../../orte/include
-I../../ompi/include -I../../oshmem/include
-I../../opal/mca/hwloc/hwloc191/hwloc/include/private/autogen
-I../../opal/mca/hwloc/hwloc191/hwloc/include/hwloc/autogen -I../..
-I/work/pi/src/openmpi-1.8.5/opal/mca/hwloc/hwloc191/hwloc/include
-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent

-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent/include
-march=armv7 -MT atomic-asm.lo -MD -MP -MF
.deps/atomic-asm.Tpo -c atomic-asm.S  -fPIC -DPIC -o
.libs/atomic-asm.o^M
atomic-asm.S:1:0: error: target CPU does not support ARM mode

which is very puzzling ...

can you confirm
1) you are not cross compiling
2) your gcc can generate code for armv7 ?

Cheers,

Gilles




On 6/9/2015 1:48 AM, Jeff Layton wrote:

Jeff,

Sorry - I was traveling for a week and didn't have to
the RPi.

What happens if you don't supply CCASFLAGS at all?


The output from "make" is below. It died when it tried
to compile
atomic-local. It says the processor doesn't support
ARM mode "dmb".

Thanks!

Jeff



pi@raspberrypi /work/pi/src/openmpi-1.8.5 $ make
Making all in config
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/config'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory
'/work/pi/src/openmpi-1.8.5/config'
Making all in contrib
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/contrib'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory
'/work/pi/src/openmpi-1.8.5/contrib'
Making all in opal
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal'
Making all in include
make[2]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make  all-am
make[3]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make[3]: Leaving directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make[2]: Leaving directory
'/work/pi/src/openmpi-1.8.5/opal/include'
Making all in asm
make[2]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/asm'
  CC   asm.lo
rm -f atomic-asm.S
ln -s "../../opal/asm/generated/atomic-local.s"
atomic-asm.S
  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'

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

2015-06-09 Thread Jeff Layton


Gilles,

Yes I can. I tried a simple C code ("hello world") and it compiled
and ran correctly.

Thanks!

Jeff


Jeff,

can you
gcc -march=armv7-a foo.c

Cheers,

Gilles

On Tuesday, June 9, 2015, Jeff Layton > wrote:


Gilles,

I'm not cross-compiling - I'm building on the Pi 2.

I'm not sure how to check if gcc can generate armv7 code.
I'm using Raspbian and I'm just using the default compilers
that come with it (I think it's gcc 4.6.3).

Thanks!

Jeff

Jeff,

dmb is available only on ARMv7 (Pi 2)

if i remember correctly, you are building Open MPI on ARMv7 as
well (Pi 2),
so this is not a cross compilation issue.

if you configure with -march=armv7, the relevant log is
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I.
-I../../opal/include -I../../orte/include -I../../ompi/include
-I../../oshmem/include
-I../../opal/mca/hwloc/hwloc191/hwloc/include/private/autogen
-I../../opal/mca/hwloc/hwloc191/hwloc/include/hwloc/autogen
-I../..
-I/work/pi/src/openmpi-1.8.5/opal/mca/hwloc/hwloc191/hwloc/include
-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent

-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent/include
-march=armv7 -MT atomic-asm.lo -MD -MP -MF
.deps/atomic-asm.Tpo -c atomic-asm.S  -fPIC -DPIC -o
.libs/atomic-asm.o^M
atomic-asm.S:1:0: error: target CPU does not support ARM mode

which is very puzzling ...

can you confirm
1) you are not cross compiling
2) your gcc can generate code for armv7 ?

Cheers,

Gilles




On 6/9/2015 1:48 AM, Jeff Layton wrote:

Jeff,

Sorry - I was traveling for a week and didn't have to the RPi.

What happens if you don't supply CCASFLAGS at all?


The output from "make" is below. It died when it tried to
compile
atomic-local. It says the processor doesn't support ARM
mode "dmb".

Thanks!

Jeff



pi@raspberrypi /work/pi/src/openmpi-1.8.5 $ make
Making all in config
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/config'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/config'
Making all in contrib
make[1]: Entering directory
'/work/pi/src/openmpi-1.8.5/contrib'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory
'/work/pi/src/openmpi-1.8.5/contrib'
Making all in opal
make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/opal'
Making all in include
make[2]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make  all-am
make[3]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make[3]: Leaving directory
'/work/pi/src/openmpi-1.8.5/opal/include'
make[2]: Leaving directory
'/work/pi/src/openmpi-1.8.5/opal/include'
Making all in asm
make[2]: Entering directory
'/work/pi/src/openmpi-1.8.5/opal/asm'
  CC   asm.lo
rm -f atomic-asm.S
ln -s "../../opal/asm/generated/atomic-local.s" atomic-asm.S
  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

Re: [OMPI users] building openmpi-v1.10-dev-59-g4e9cea6 still breaks

2015-06-09 Thread Nathan Hjelm


Bah. Another proc->super usage. Thought I got them all. Will fix now.

-Nathan

On Tue, Jun 09, 2015 at 12:43:50PM +0200, Siegmar Gross wrote:
> Hi,
> 
> today I tried to build openmpi-v1.10-dev-41-g57faa88 on my machines
> (Solaris 10 Sparc, Solaris 10 x86_64, and openSUSE Linux 12.1
> x86_64) with gcc-4.9.2 and Sun C 5.13 and I got the following error
> on all platforms with cc. I have already reported the problem a few
> days ago. Nathan wanted to fix it and I'm not sure if he hasn't had
> time to do it or if it is something different now
> (https://github.com/open-mpi/ompi-release/pull/299). I used the
> following command to configure the package.
> 
> ../openmpi-v1.10-dev-59-g4e9cea6/configure 
> --prefix=/usr/local/openmpi-1.10.0_64_gcc \
>   --libdir=/usr/local/openmpi-1.10.0_64_gcc/lib64 \
>   --with-jdk-bindir=/usr/local/jdk1.8.0/bin \
>   --with-jdk-headers=/usr/local/jdk1.8.0/include \
>   JAVA_HOME=/usr/local/jdk1.8.0 \
>   LDFLAGS="-m64" CC="gcc" CXX="g++" FC="gfortran" \
>   CFLAGS="-m64" CXXFLAGS="-m64" FCFLAGS="-m64" \
>   CPP="cpp" CXXCPP="cpp" \
>   CPPFLAGS="" CXXCPPFLAGS="" \
>   --enable-mpi-cxx \
>   --enable-cxx-exceptions \
>   --enable-mpi-java \
>   --enable-heterogeneous \
>   --enable-mpi-thread-multiple \
>   --with-hwloc=internal \
>   --without-verbs \
>   --with-wrapper-cflags="-std=c11 -m64" \
>   --with-wrapper-cxxflags="-m64" \
>   --with-wrapper-fcflags="-m64" \
>   --enable-debug \
>   |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc
> 
> 
> ...
>   CC   osc_pt2pt_data_move.lo
> ../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c:
>  In function 'osc_pt2pt_accumulate_buffer':
> ../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c:571:20:
>  error: 'opal_list_item_t' has no member named 'proc_arch'
>  if (proc->super.proc_arch != ompi_proc_local()->super.proc_arch) {
> ^
> ../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c:571:58:
>  error: 'opal_list_item_t' has no member named 'proc_arch'
>  if (proc->super.proc_arch != ompi_proc_local()->super.proc_arch) {
>   ^
> make[2]: *** [osc_pt2pt_data_move.lo] Error 1
> make[2]: Leaving directory 
> `/export2/src/openmpi-1.10.0/openmpi-v1.10-dev-59-g4e9cea6-SunOS.sparc.64_gcc/ompi/mca/osc/pt2pt'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory 
> `/export2/src/openmpi-1.10.0/openmpi-v1.10-dev-59-g4e9cea6-SunOS.sparc.64_gcc/ompi'
> make: *** [all-recursive] Error 1
> tyr openmpi-v1.10-dev-59-g4e9cea6-SunOS.sparc.64_gcc 122 
> 
> 
> 
> 
> ...
>   CC   osc_pt2pt_data_move.lo
> "../../../../../openmpi-v1.10-dev-59-g4e9cea6/opal/include/opal/sys/amd64/atomic.h",
>  line 136: warning: parameter in inline asm statement unused: %3
> "../../../../../openmpi-v1.10-dev-59-g4e9cea6/opal/include/opal/sys/amd64/atomic.h",
>  line 182: warning: parameter in inline asm statement unused: %2
> "../../../../../openmpi-v1.10-dev-59-g4e9cea6/opal/include/opal/sys/amd64/atomic.h",
>  line 203: warning: parameter in inline asm statement unused: %2
> "../../../../../openmpi-v1.10-dev-59-g4e9cea6/opal/include/opal/sys/amd64/atomic.h",
>  line 224: warning: parameter in inline asm statement unused: %2
> "../../../../../openmpi-v1.10-dev-59-g4e9cea6/opal/include/opal/sys/amd64/atomic.h",
>  line 245: warning: parameter in inline asm statement unused: %2
> "../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c",
>  line 571: improper member use: proc_arch
> "../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c",
>  line 571: improper member use: proc_arch
> cc: acomp failed for 
> ../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c
> make[2]: *** [osc_pt2pt_data_move.lo] Error 1
> make[2]: Leaving directory 
> `/export2/src/openmpi-1.10.0/openmpi-v1.10-dev-59-g4e9cea6-Linux.x86_64.64_cc/ompi/mca/osc/pt2pt'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory 
> `/export2/src/openmpi-1.10.0/openmpi-v1.10-dev-59-g4e9cea6-Linux.x86_64.64_cc/ompi'
> make: *** [all-recursive] Error 1
> linpc1 openmpi-v1.10-dev-59-g4e9cea6-Linux.x86_64.64_cc 197 
> 
> 
> I would be grateful, if somebody could fix the problem. Thank
> you very much for any help in advance.
> 
> 
> Kind regards
> 
> Siegmar
> 
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/06/27056.php


pgpRwWQTTyVjw.pgp
Description: PGP signature

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

2015-06-09 Thread Gilles Gouaillardet

Jeff,

btw, did you try a pI 1 before a pi2 ?

I checked some forums, and you will likely have to upgrade gcc to 4.8

a simpler option could be linaro
https://www.raspberrypi.org/forums/viewtopic.php?f=56=98997

Cheers,

Gilles

On Tuesday, June 9, 2015, Gilles Gouaillardet 
wrote:

> Jeff,
>
> can you
> gcc -march=armv7-a foo.c
>
> Cheers,
>
> Gilles
>
> On Tuesday, June 9, 2015, Jeff Layton  > wrote:
>
>> Gilles,
>>
>> I'm not cross-compiling - I'm building on the Pi 2.
>>
>> I'm not sure how to check if gcc can generate armv7 code.
>> I'm using Raspbian and I'm just using the default compilers
>> that come with it (I think it's gcc 4.6.3).
>>
>> Thanks!
>>
>> Jeff
>>
>>  Jeff,
>>>
>>> dmb is available only on ARMv7 (Pi 2)
>>>
>>> if i remember correctly, you are building Open MPI on ARMv7 as well (Pi
>>> 2),
>>> so this is not a cross compilation issue.
>>>
>>> if you configure with -march=armv7, the relevant log is
>>> libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I.
>>> -I../../opal/include -I../../orte/include -I../../ompi/include
>>> -I../../oshmem/include
>>> -I../../opal/mca/hwloc/hwloc191/hwloc/include/private/autogen
>>> -I../../opal/mca/hwloc/hwloc191/hwloc/include/hwloc/autogen -I../..
>>> -I/work/pi/src/openmpi-1.8.5/opal/mca/hwloc/hwloc191/hwloc/include
>>> -I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent
>>> -I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent/include
>>> -march=armv7 -MT atomic-asm.lo -MD -MP -MF .deps/atomic-asm.Tpo -c
>>> atomic-asm.S  -fPIC -DPIC -o .libs/atomic-asm.o^M
>>> atomic-asm.S:1:0: error: target CPU does not support ARM mode
>>>
>>> which is very puzzling ...
>>>
>>> can you confirm
>>> 1) you are not cross compiling
>>> 2) your gcc can generate code for armv7 ?
>>>
>>> Cheers,
>>>
>>> Gilles
>>>
>>>
>>>
>>>
>>> On 6/9/2015 1:48 AM, Jeff Layton wrote:
>>>
 Jeff,

 Sorry - I was traveling for a week and didn't have to the RPi.

  What happens if you don't supply CCASFLAGS at all?
>
>
 The output from "make" is below. It died when it tried to compile
 atomic-local. It says the processor doesn't support ARM mode "dmb".

 Thanks!

 Jeff

 pi@raspberrypi /work/pi/src/openmpi-1.8.5 $ make
 Making all in config
 make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/config'
 make[1]: Nothing to be done for 'all'.
 make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/config'
 Making all in contrib
 make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/contrib'
 make[1]: Nothing to be done for 'all'.
 make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/contrib'
 Making all in opal
 make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/opal'
 Making all in include
 make[2]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/include'
 make  all-am
 make[3]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/include'
 make[3]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/include'
 make[2]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/include'
 Making all in asm
 make[2]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/asm'
   CC   asm.lo
 rm -f atomic-asm.S
 ln -s "../../opal/asm/generated/atomic-local.s" atomic-asm.S
   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:1608: recipe for target 'atomic-asm.lo' failed
 make[2]: *** [atomic-asm.lo] Error 1
 make[2]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/asm'
 Makefile:2149: recipe for target 'all-recursive' failed
 make[1]: *** [all-recursive] Error 1
 make[1]:

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

2015-06-09 Thread Gilles Gouaillardet

Jeff,

can you
gcc -march=armv7-a foo.c

Cheers,

Gilles

On Tuesday, June 9, 2015, Jeff Layton  wrote:

> Gilles,
>
> I'm not cross-compiling - I'm building on the Pi 2.
>
> I'm not sure how to check if gcc can generate armv7 code.
> I'm using Raspbian and I'm just using the default compilers
> that come with it (I think it's gcc 4.6.3).
>
> Thanks!
>
> Jeff
>
>  Jeff,
>>
>> dmb is available only on ARMv7 (Pi 2)
>>
>> if i remember correctly, you are building Open MPI on ARMv7 as well (Pi
>> 2),
>> so this is not a cross compilation issue.
>>
>> if you configure with -march=armv7, the relevant log is
>> libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I.
>> -I../../opal/include -I../../orte/include -I../../ompi/include
>> -I../../oshmem/include
>> -I../../opal/mca/hwloc/hwloc191/hwloc/include/private/autogen
>> -I../../opal/mca/hwloc/hwloc191/hwloc/include/hwloc/autogen -I../..
>> -I/work/pi/src/openmpi-1.8.5/opal/mca/hwloc/hwloc191/hwloc/include
>> -I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent
>> -I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent/include
>> -march=armv7 -MT atomic-asm.lo -MD -MP -MF .deps/atomic-asm.Tpo -c
>> atomic-asm.S  -fPIC -DPIC -o .libs/atomic-asm.o^M
>> atomic-asm.S:1:0: error: target CPU does not support ARM mode
>>
>> which is very puzzling ...
>>
>> can you confirm
>> 1) you are not cross compiling
>> 2) your gcc can generate code for armv7 ?
>>
>> Cheers,
>>
>> Gilles
>>
>>
>>
>>
>> On 6/9/2015 1:48 AM, Jeff Layton wrote:
>>
>>> Jeff,
>>>
>>> Sorry - I was traveling for a week and didn't have to the RPi.
>>>
>>>  What happens if you don't supply CCASFLAGS at all?


>>> The output from "make" is below. It died when it tried to compile
>>> atomic-local. It says the processor doesn't support ARM mode "dmb".
>>>
>>> Thanks!
>>>
>>> Jeff
>>>
>>>
>>>
>>> pi@raspberrypi /work/pi/src/openmpi-1.8.5 $ make
>>> Making all in config
>>> make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/config'
>>> make[1]: Nothing to be done for 'all'.
>>> make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/config'
>>> Making all in contrib
>>> make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/contrib'
>>> make[1]: Nothing to be done for 'all'.
>>> make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/contrib'
>>> Making all in opal
>>> make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/opal'
>>> Making all in include
>>> make[2]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/include'
>>> make  all-am
>>> make[3]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/include'
>>> make[3]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/include'
>>> make[2]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/include'
>>> Making all in asm
>>> make[2]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/asm'
>>>   CC   asm.lo
>>> rm -f atomic-asm.S
>>> ln -s "../../opal/asm/generated/atomic-local.s" atomic-asm.S
>>>   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:1608: recipe for target 'atomic-asm.lo' failed
>>> make[2]: *** [atomic-asm.lo] Error 1
>>> make[2]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/asm'
>>> Makefile:2149: recipe for target 'all-recursive' failed
>>> make[1]: *** [all-recursive] Error 1
>>> make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal'
>>> Makefile:1698: recipe for target 'all-recursive' failed
>>> make: *** [all-recursive] Error 1
>>>
>>> ___
>>> users mailing list
>>> us...@open-mpi.org
>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>>> Link to this post:
>>> http://www.open-mpi.org/community/lists/users/2015/06/27050.php
>>>
>>>
>> ___
>> users mailing list
>> us...@open-mpi.org

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

2015-06-09 Thread Jeff Layton


Gilles,

I'm not cross-compiling - I'm building on the Pi 2.

I'm not sure how to check if gcc can generate armv7 code.
I'm using Raspbian and I'm just using the default compilers
that come with it (I think it's gcc 4.6.3).

Thanks!

Jeff


Jeff,

dmb is available only on ARMv7 (Pi 2)

if i remember correctly, you are building Open MPI on ARMv7 as well 
(Pi 2),

so this is not a cross compilation issue.

if you configure with -march=armv7, the relevant log is
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. 
-I../../opal/include -I../../orte/include -I../../ompi/include 
-I../../oshmem/include 
-I../../opal/mca/hwloc/hwloc191/hwloc/include/private/autogen 
-I../../opal/mca/hwloc/hwloc191/hwloc/include/hwloc/autogen -I../.. 
-I/work/pi/src/openmpi-1.8.5/opal/mca/hwloc/hwloc191/hwloc/include 
-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent 
-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent/include 
-march=armv7 -MT atomic-asm.lo -MD -MP -MF .deps/atomic-asm.Tpo -c 
atomic-asm.S  -fPIC -DPIC -o .libs/atomic-asm.o^M

atomic-asm.S:1:0: error: target CPU does not support ARM mode

which is very puzzling ...

can you confirm
1) you are not cross compiling
2) your gcc can generate code for armv7 ?

Cheers,

Gilles




On 6/9/2015 1:48 AM, Jeff Layton wrote:

Jeff,

Sorry - I was traveling for a week and didn't have to the RPi.


What happens if you don't supply CCASFLAGS at all?



The output from "make" is below. It died when it tried to compile
atomic-local. It says the processor doesn't support ARM mode "dmb".

Thanks!

Jeff



pi@raspberrypi /work/pi/src/openmpi-1.8.5 $ make
Making all in config
make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/config'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/config'
Making all in contrib
make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/contrib'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/contrib'
Making all in opal
make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/opal'
Making all in include
make[2]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/include'
make  all-am
make[3]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/include'
make[3]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/include'
make[2]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/include'
Making all in asm
make[2]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/asm'
  CC   asm.lo
rm -f atomic-asm.S
ln -s "../../opal/asm/generated/atomic-local.s" atomic-asm.S
  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:1608: recipe for target 'atomic-asm.lo' failed
make[2]: *** [atomic-asm.lo] Error 1
make[2]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/asm'
Makefile:2149: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal'
Makefile:1698: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2015/06/27050.php




___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2015/06/27055.php

[OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

2015-06-09 Thread Siegmar Gross

Hi,

today I tried to build openmpi-v1.8.5-46-g9f5f498 on my machines
(Solaris 10 Sparc, Solaris 10 x86_64, and openSUSE Linux 12.1
x86_64) with gcc-4.9.2 and Sun C 5.13 and I got the same error
on all three platforms with both compilers. I have already
reported the problem a few days ago. I used the following command
to configure the package.

../openmpi-v1.8.5-46-g9f5f498/configure \
  --prefix=/usr/local/openmpi-1.8.6_64_gcc \
  --libdir=/usr/local/openmpi-1.8.6_64_gcc/lib64 \
  --with-jdk-bindir=/usr/local/jdk1.8.0/bin \
  --with-jdk-headers=/usr/local/jdk1.8.0/include \
  JAVA_HOME=/usr/local/jdk1.8.0 \
  LDFLAGS="-m64" CC="gcc" CXX="g++" FC="gfortran" \
  CFLAGS="-m64" CXXFLAGS="-m64" FCFLAGS="-m64" \
  CPP="cpp" CXXCPP="cpp" \
  CPPFLAGS="" CXXCPPFLAGS="" \
  --enable-mpi-cxx \
  --enable-cxx-exceptions \
  --enable-mpi-java \
  --enable-heterogeneous \
  --enable-mpi-thread-multiple \
  --with-threads=posix \
  --with-hwloc=internal \
  --without-verbs \
  --with-wrapper-cflags="-std=c11 -m64" \
  --with-wrapper-cxxflags="-m64" \
  --with-wrapper-fcflags="-m64" \
  --enable-debug \
  |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc


...
make[3]: Entering directory 
`/export2/src/openmpi-1.8.6/openmpi-1.8.6-Linux.x86_64.64_gcc/ompi/include'
../../../openmpi-v1.8.5-46-g9f5f498/ompi/mpi/fortran/base/gen-mpi-sizeof.pl \
--header=mpif-sizeof.h --ierror=mandatory \
--maxrank=7 \
--generate=1 \
--real16=1 \
--complex32=1
ln -s 
../../../openmpi-v1.8.5-46-g9f5f498/opal/include/opal/opal_portable_platform.h 
mpi_portable_platform.h
ln: failed to create symbolic link `mpi_portable_platform.h': File exists
make[3]: *** [mpi_portable_platform.h] Error 1
make[3]: Leaving directory 
`/export2/src/openmpi-1.8.6/openmpi-1.8.6-Linux.x86_64.64_gcc/ompi/include'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/export2/src/openmpi-1.8.6/openmpi-1.8.6-Linux.x86_64.64_gcc/ompi/include'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/export2/src/openmpi-1.8.6/openmpi-1.8.6-Linux.x86_64.64_gcc/ompi'
make: *** [all-recursive] Error 1
linpc1 openmpi-1.8.6-Linux.x86_64.64_gcc 261 


I would be grateful, if somebody could fix the problem. Thank
you very much for any help in advance.


Kind regards

Siegmar

[OMPI users] building openmpi-v1.10-dev-59-g4e9cea6 still breaks

2015-06-09 Thread Siegmar Gross

Hi,

today I tried to build openmpi-v1.10-dev-41-g57faa88 on my machines
(Solaris 10 Sparc, Solaris 10 x86_64, and openSUSE Linux 12.1
x86_64) with gcc-4.9.2 and Sun C 5.13 and I got the following error
on all platforms with cc. I have already reported the problem a few
days ago. Nathan wanted to fix it and I'm not sure if he hasn't had
time to do it or if it is something different now
(https://github.com/open-mpi/ompi-release/pull/299). I used the
following command to configure the package.

../openmpi-v1.10-dev-59-g4e9cea6/configure 
--prefix=/usr/local/openmpi-1.10.0_64_gcc \
  --libdir=/usr/local/openmpi-1.10.0_64_gcc/lib64 \
  --with-jdk-bindir=/usr/local/jdk1.8.0/bin \
  --with-jdk-headers=/usr/local/jdk1.8.0/include \
  JAVA_HOME=/usr/local/jdk1.8.0 \
  LDFLAGS="-m64" CC="gcc" CXX="g++" FC="gfortran" \
  CFLAGS="-m64" CXXFLAGS="-m64" FCFLAGS="-m64" \
  CPP="cpp" CXXCPP="cpp" \
  CPPFLAGS="" CXXCPPFLAGS="" \
  --enable-mpi-cxx \
  --enable-cxx-exceptions \
  --enable-mpi-java \
  --enable-heterogeneous \
  --enable-mpi-thread-multiple \
  --with-hwloc=internal \
  --without-verbs \
  --with-wrapper-cflags="-std=c11 -m64" \
  --with-wrapper-cxxflags="-m64" \
  --with-wrapper-fcflags="-m64" \
  --enable-debug \
  |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc


...
  CC   osc_pt2pt_data_move.lo
../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c:
 In function 'osc_pt2pt_accumulate_buffer':
../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c:571:20:
 error: 'opal_list_item_t' has no member named 'proc_arch'
 if (proc->super.proc_arch != ompi_proc_local()->super.proc_arch) {
^
../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c:571:58:
 error: 'opal_list_item_t' has no member named 'proc_arch'
 if (proc->super.proc_arch != ompi_proc_local()->super.proc_arch) {
  ^
make[2]: *** [osc_pt2pt_data_move.lo] Error 1
make[2]: Leaving directory 
`/export2/src/openmpi-1.10.0/openmpi-v1.10-dev-59-g4e9cea6-SunOS.sparc.64_gcc/ompi/mca/osc/pt2pt'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/export2/src/openmpi-1.10.0/openmpi-v1.10-dev-59-g4e9cea6-SunOS.sparc.64_gcc/ompi'
make: *** [all-recursive] Error 1
tyr openmpi-v1.10-dev-59-g4e9cea6-SunOS.sparc.64_gcc 122 




...
  CC   osc_pt2pt_data_move.lo
"../../../../../openmpi-v1.10-dev-59-g4e9cea6/opal/include/opal/sys/amd64/atomic.h",
 line 136: warning: parameter in inline asm statement unused: %3
"../../../../../openmpi-v1.10-dev-59-g4e9cea6/opal/include/opal/sys/amd64/atomic.h",
 line 182: warning: parameter in inline asm statement unused: %2
"../../../../../openmpi-v1.10-dev-59-g4e9cea6/opal/include/opal/sys/amd64/atomic.h",
 line 203: warning: parameter in inline asm statement unused: %2
"../../../../../openmpi-v1.10-dev-59-g4e9cea6/opal/include/opal/sys/amd64/atomic.h",
 line 224: warning: parameter in inline asm statement unused: %2
"../../../../../openmpi-v1.10-dev-59-g4e9cea6/opal/include/opal/sys/amd64/atomic.h",
 line 245: warning: parameter in inline asm statement unused: %2
"../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c",
 line 571: improper member use: proc_arch
"../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c",
 line 571: improper member use: proc_arch
cc: acomp failed for 
../../../../../openmpi-v1.10-dev-59-g4e9cea6/ompi/mca/osc/pt2pt/osc_pt2pt_data_move.c
make[2]: *** [osc_pt2pt_data_move.lo] Error 1
make[2]: Leaving directory 
`/export2/src/openmpi-1.10.0/openmpi-v1.10-dev-59-g4e9cea6-Linux.x86_64.64_cc/ompi/mca/osc/pt2pt'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/export2/src/openmpi-1.10.0/openmpi-v1.10-dev-59-g4e9cea6-Linux.x86_64.64_cc/ompi'
make: *** [all-recursive] Error 1
linpc1 openmpi-v1.10-dev-59-g4e9cea6-Linux.x86_64.64_cc 197 


I would be grateful, if somebody could fix the problem. Thank
you very much for any help in advance.


Kind regards

Siegmar

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

2015-06-09 Thread Gilles Gouaillardet


Jeff,

dmb is available only on ARMv7 (Pi 2)

if i remember correctly, you are building Open MPI on ARMv7 as well (Pi 2),
so this is not a cross compilation issue.

if you configure with -march=armv7, the relevant log is
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. 
-I../../opal/include -I../../orte/include -I../../ompi/include 
-I../../oshmem/include 
-I../../opal/mca/hwloc/hwloc191/hwloc/include/private/autogen 
-I../../opal/mca/hwloc/hwloc191/hwloc/include/hwloc/autogen -I../.. 
-I/work/pi/src/openmpi-1.8.5/opal/mca/hwloc/hwloc191/hwloc/include 
-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent 
-I/work/pi/src/openmpi-1.8.5/opal/mca/event/libevent2021/libevent/include -march=armv7 
-MT atomic-asm.lo -MD -MP -MF .deps/atomic-asm.Tpo -c atomic-asm.S  
-fPIC -DPIC -o .libs/atomic-asm.o^M

atomic-asm.S:1:0: error: target CPU does not support ARM mode

which is very puzzling ...

can you confirm
1) you are not cross compiling
2) your gcc can generate code for armv7 ?

Cheers,

Gilles




On 6/9/2015 1:48 AM, Jeff Layton wrote:

Jeff,

Sorry - I was traveling for a week and didn't have to the RPi.


What happens if you don't supply CCASFLAGS at all?



The output from "make" is below. It died when it tried to compile
atomic-local. It says the processor doesn't support ARM mode "dmb".

Thanks!

Jeff



pi@raspberrypi /work/pi/src/openmpi-1.8.5 $ make
Making all in config
make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/config'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/config'
Making all in contrib
make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/contrib'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/contrib'
Making all in opal
make[1]: Entering directory '/work/pi/src/openmpi-1.8.5/opal'
Making all in include
make[2]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/include'
make  all-am
make[3]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/include'
make[3]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/include'
make[2]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/include'
Making all in asm
make[2]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/asm'
  CC   asm.lo
rm -f atomic-asm.S
ln -s "../../opal/asm/generated/atomic-local.s" atomic-asm.S
  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:1608: recipe for target 'atomic-asm.lo' failed
make[2]: *** [atomic-asm.lo] Error 1
make[2]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal/asm'
Makefile:2149: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/work/pi/src/openmpi-1.8.5/opal'
Makefile:1698: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2015/06/27050.php

Re: [OMPI users] Bug: Disabled mpi_leave_pinned for GPUDirect and InfiniBand during run-time caused by GCC optimizations

2015-06-09 Thread Gilles Gouaillardet

i wrote a reproducer i sent to the GCC folks
https://gcc.gnu.org/ml/gcc-bugs/2015-06/msg00757.html

Cheers,

Gilles

On Tue, Jun 9, 2015 at 3:20 AM, Jeff Squyres (jsquyres)
 wrote:
> On Jun 8, 2015, at 11:27 AM, Dave Goodell (dgoodell)  
> wrote:
>>
>> My suggestion is to try to create a small reproducer program that we can 
>> send to the GCC folks with the claim that we believe it to be a buggy 
>> optimization.  Then we can see whether they agree and if not, how they 
>> defend that behavior.
>>
>> We probably still need a workaround for now though, and the "volatile" 
>> approach seems fine to me.
>
> +1
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/06/27051.php

Re: [OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

Re: [OMPI users] building openmpi-v1.10-dev-59-g4e9cea6 still breaks

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

[OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

[OMPI users] building openmpi-v1.10-dev-59-g4e9cea6 still breaks

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

Re: [OMPI users] Bug: Disabled mpi_leave_pinned for GPUDirect and InfiniBand during run-time caused by GCC optimizations

14 matches

Site Navigation

Mail list logo

Footer information