Setting up compiler

[Romme]

Hi

I have been trying to set up the Red Pitaya compiler on Ubuntu 14.04 some quite some time now. It seems that I have now run into an error that I can't find mention of through google.

I have installed Vivado and the Linaro ARM toolchain and cloned RedPitaya from github. Running make ends in:

Code: Select all

make -C tmp/u-boot-xlnx-xilinx-v2015.4 arch=ARM CFLAGS="-O2 -mtune=cortex-a9 -mfpu=neon -mfloat-abi=hard" all
make[1]: Går til katalog '/home/martin/Programmering/RedPitaya/tmp/u-boot-xlnx-xilinx-v2015.4'
scripts/kconfig/conf --silentoldconfig Kconfig
  CHK     include/config.h
  UPD     include/config.h
  GEN     include/autoconf.mk
  GEN     include/autoconf.mk.dep
  GEN     spl/include/autoconf.mk
make[1]: Forlader katalog '/home/martin/Programmering/RedPitaya/tmp/u-boot-xlnx-xilinx-v2015.4'
make[1]: Går til katalog '/home/martin/Programmering/RedPitaya/tmp/u-boot-xlnx-xilinx-v2015.4'
  CHK     include/config/uboot.release
  UPD     include/config/uboot.release
  CHK     include/generated/version_autogenerated.h
  UPD     include/generated/version_autogenerated.h
  CHK     include/generated/timestamp_autogenerated.h
  UPD     include/generated/timestamp_autogenerated.h
  CC      lib/asm-offsets.s
lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch
 /*
 ^
make[2]: *** [lib/asm-offsets.s] Error 1
make[1]: *** [prepare0] Error 2
make[1]: Forlader katalog '/home/martin/Programmering/RedPitaya/tmp/u-boot-xlnx-xilinx-v2015.4'
make: *** [tmp/u-boot.elf] Error 2

Any help will be highly appreciated.

Kind regards,
Martin Romme

[Nils Roos]

This happens when the wrong compiler is called. Did you do

Code: Select all

. settings.sh

before make ?
Did you install linaro into the default location ? If not, did you adapt settings.sh accordingly ?

[Romme]

Yes, I had forgotten '. settings.sh'.

The next error I encountered was:

Code: Select all

fatal error: sys/types.h: No such file or directory

Which I solved by installing the gcc-multilib package.

Now I stuck because cryptopp.com seems to be down. Hopefully it will be up soon.

Thank you for the help so far!

Kind regards,
Martin Romme