On May 30, 2015, at 9:42 AM, Jeff Layton <layto...@att.net> 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 this email. Ok, thanks. Here's the problematic compile command: ----- 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 ----- Stripping out the -D's and -I's which aren't important for this discussion, we're left with: ----- gcc -std=gnu99 -march=armv7 -MT atomic-asm.lo -MD -MP -MF .deps/atomic-asm.Tpo -c atomic-asm.S -fPIC -DPIC -o .libs/atomic-asm.o ----- So it looks like the -march=armv7 is, indeed, the problematic switch. FWIW, a few lines above it, this line succeeded: ----- 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 -O3 -DNDEBUG -finline-functions -fno-strict-aliasing -pthread -MT asm.lo -MD -MP -MF .deps/asm.Tpo -c asm.c -fPIC -DPIC -o .libs/asm.o ----- Which, as you notice, does *not* have the -march=armv7 token (because it's compiling a C file, not an assembly file). >>>> I used the configure flag CCASFLAGS=-march=armv7-a >>>> >>>> Not sure if that is correct or not. I'm guessing I'm using the wrong >>>> architecture for the Pi 2. Suggestions? What happens if you don't supply CCASFLAGS at all? -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
