Gilles,
I installed the 4.8 series of compilers on the Pi 2 (gcc, g++, and
gfortran).
I did a fresh untar of openmpi-1.8.5. I set the environment variables
CC, CXX, and FC to point to the 4.8 compilers. However, the build failed
again.
Making all in config
make[1]: Entering directory
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 ?)
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
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
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
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
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
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
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
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
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
On May 30, 2015, at 9:42 AM, Jeff Layton wrote:
>
> The error happens during the configure step before compiling.
Hmm -- I'm confused. You show output from "make" in your previous mails...?
> However, I ran the make command as you indicated and I'm
> attaching the output to
Jeff,
The error happens during the configure step before compiling.
However, I ran the make command as you indicated and I'm
attaching the output to this email.
Thanks!
Jeff
Can you send the output of "make V=1"?
That will show the exact command line that is being used to build that file.
Can you send the output of "make V=1"?
That will show the exact command line that is being used to build that file.
> On May 29, 2015, at 2:17 PM, Jeff Layton wrote:
>
> George,
>
> I changed my configure command to be:
>
> ./configure CCASFLAGS=-march=native
>
> and I
George,
I changed my configure command to be:
./configure CCASFLAGS=-march=native
and I get an error while running configure:
...
*** Assembler
checking dependency style of gcc -std=gnu99... gcc3
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister
As you are not cross-compiling I would expect gcc to use the right assembly
by default. What is happening is you force the native mode (-march=native) ?
George.
On Fri, May 29, 2015 at 10:09 AM, Jeff Layton wrote:
> On 05/29/2015 09:35 AM, Jeff Layton wrote:
>
> Gilles,
>
On 05/29/2015 09:35 AM, Jeff Layton wrote:
Gilles,
oops - yes, CFLAGS. But I also saw this posting:
https://www.open-mpi.org/community/lists/users/2013/01/2.php
where CCASFLAGS is used (I assume because for asm). I'm trying
this flag when I configure Open MPI.
I tried using the
Gilles,
oops - yes, CFLAGS. But I also saw this posting:
https://www.open-mpi.org/community/lists/users/2013/01/2.php
where CCASFLAGS is used (I assume because for asm). I'm trying
this flag when I configure Open MPI.
Thanks!
Jeff
Jeff,
shall I assume you made a typo and wrote
Jeff,
shall I assume you made a typo and wrote CCFLAGS instead of CFLAGS ?
also, can you double check the flags are correctly passed to the assembler
with
cd opal/asm
make -n atomic-asm.lo
Cheers,
Gilles
On Friday, May 29, 2015, Jeff Layton wrote:
> Good morning,
>
> I'm
Good morning,
I'm building OpenMPI from source on a Raspberry Pi 2 and
I've hit an error. The error is:
make[2]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/asm'
CPPASatomic-asm.lo
atomic-asm.S: Assembler messages:
atomic-asm.S:7: Error: selected processor does not support ARM
20 matches
Mail list logo