lr-mame (in experimental) will not install

simonster

Hi

Has anyone managed to get lr-mame to install?

Whenever I try, it goes off for about five minutes and then fails.

The tail of the log is below:

lapi.c
gcc -O3 -mcpu=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -funsafe-math-optimizations -pipe -MMD -MP -MP -DNDEBUG -DLUA_COMPAT_MODULE -DLUA_USE_POSIX -DLUA_USE_DLOPEN -I../../src/host/lua-5.3.0/src -Wall -Wextra -Os -o "obj/Release/src/host/lua-5.3.0/src/lapi.o" -c "../../src/host/lua-5.3.0/src/lapi.c"
gcc: error: unrecognized argument in option ‘-mcpu=cortex-a53’
gcc: note: valid arguments to ‘-mcpu=’ are: arm1020e arm1020t arm1022e arm1026ej-s arm10e arm10tdmi arm1136j-s arm1136jf-s arm1156t2-s arm1156t2f-s arm1176jz-s arm1176jzf-s arm2 arm250 arm3 arm6 arm60 arm600 arm610 arm620 arm7 arm70 arm700 arm700i arm710 arm7100 arm710c arm710t arm720 arm720t arm740t arm7500 arm7500fe arm7d arm7di arm7dm arm7dmi arm7m arm7tdmi arm7tdmi-s arm8 arm810 arm9 arm920 arm920t arm922t arm926ej-s arm940t arm946e-s arm966e-s arm968e-s arm9e arm9tdmi cortex-a15 cortex-a5 cortex-a7 cortex-a8 cortex-a9 cortex-m0 cortex-m1 cortex-m3 cortex-m4 cortex-r4 cortex-r4f cortex-r5 ep9312 fa526 fa606te fa626 fa626te fa726te fmp626 generic-armv7-a iwmmxt iwmmxt2 mpcore mpcorenovfp native strongarm strongarm110 strongarm1100 strongarm1110 xscale
gcc: error: unrecognized argument in option ‘-mfpu=neon-fp-armv8’
gcc: note: valid arguments to ‘-mfpu=’ are: fpa fpe2 fpe3 fpv4-sp-d16 maverick neon neon-fp16 neon-vfpv4 vfp vfp3 vfpv3 vfpv3-d16 vfpv3-d16-fp16 vfpv3-fp16 vfpv3xd vfpv3xd-fp16 vfpv4 vfpv4-d16
genie.make:249: recipe for target 'obj/Release/src/host/lua-5.3.0/src/lapi.o' failed

This is on a Pi3 using RetroPie 3.8.1 (installed from SD Image) with RetroPie Setup 4.0-beta2 (commit 169592f)

Any ideas?

Thanks

Simon

BuZz

@simonster what is the output of gcc -v ? Sounds like you have an older compiler as default not the Jessie gcc 4.9

If you don't want to change your default gcc you can build for rpi2 (which it will understand the cpu flags of, and will make no performance difference from my testing)

sudo __platform=rpi2 ./retropie_packages.sh lr-mame

If gcc is older, can you remember what you may have done on the system that could have changed this ? anything you have installed manually (or via retropie-setup) ?

simonster

Hi @BuZz

gcc -v returns version 4.7.3 (Raspian 4.7.3-11+rpi1)

I don't think I've done anything to change gcc and sudo apt-get gcc returns that gcc is already the newest version.

This answers why I can't compile from source, but how do I fix it?

Thanks

Simon

simonster

Ok, so I have found that I have both gcc-47 and gcc-49 in /bin/usr

Is it as simple as changing the symbolic link for gcc to point at gcc-49?

Thanks

Simon

BuZz

@simonster or update retropie setup as I've forced it. I am interested to know how you got the old GCC as default though.

simonster

Thanks for your help @BuZz , it is now compiling.

I think I have found out what happened. When I updated to RetroPie 3.7, I had to compile mk_arcade_joystick_rpi from https://github.com/recalbox/mk_arcade_joystick_rpi and it wouldn't compile as the headers package it used from http://www.niksula.hut.fi/~mhiienka/Rpi/linux-headers-rpi wouldn't compile correctly. In order to indentify the issue, I followed the manual installation rather than the package instructions and these included this line:

sudo apt-get install -y --force-yes dkms cpp-4.7 gcc-4.7 git joystick

I can only assume that gcc-4.7 installation overwrote the original symlink for gcc.

Simon

BuZz

Thanks. I suspected it might be something like that, although I don't think installing gcc-4.7 should modify the default gcc itself - at least it didn't when I tested just now - maybe some build script did it (perhaps in an older retropie).

it should be ok now we are forcing 4.9 now.