Mame2003-Plus installation problem [RetroPie 4.4 Official]

roslof

Having difficulty installing MAME2003-Plus from Source after a clean imaging of RetroPie 4.4 official. FWIW, this is being installed on a Pi 3B+, and I have installed this from source in the past with unofficial RetroPie Stretch without trouble. Wondering if somebody could help diagnose what the issue is during the build. I can navigate Unix just fine, but I'm not very savvy with translating build logs.

Here is the tail of the log file that was generated during the build:

cc -DINLINE="static __inline__" -D__LIBRETRO__ -DPI=3.1415927 -DM_PI=3.1415927 -Dasm=__asm__ -DHAS_ADSP2100=1 -DHAS_ADSP2101=1 -DHAS_ADSP2104=1 -DHAS_ADSP2105=1 -DHAS_ADSP2115=1 -DHAS_Z80=1 -DHAS_Z180=1 -DHAS_8080=1 -DHAS_8085A=1 -DHAS_M6502=1 -DHAS_M65C02=1 -DHAS_M65SC02=0 -DHAS_M65CE02=0 -DHAS_M6509=0 -DHAS_M6510=1 -DHAS_M6510T=0 -DHAS_M7501=0 -DHAS_M8502=0 -DHAS_N2A03=1 -DHAS_DECO16=1 -DHAS_M4510=0 -DHAS_H6280=1 -DHAS_I86=1 -DHAS_I88=0 -DHAS_I186=1 -DHAS_I188=0 -DHAS_I286=0 -DHAS_V20=1 -DHAS_V30=1 -DHAS_V33=1 -DHAS_V60=1 -DHAS_V70=1 -DHAS_I8035=1 -DHAS_I8039=1 -DHAS_I8048=1 -DHAS_N7751=1 -DHAS_I8X41=1 -DHAS_M6800=1 -DHAS_M6801=1 -DHAS_M6802=1 -DHAS_M6803=1 -DHAS_M6808=1 -DHAS_HD63701=1 -DHAS_NSC8105=1 -DHAS_M6805=1 -DHAS_M68705=1 -DHAS_HD63705=1 -DHAS_HD6309=1 -DHAS_M6809=1 -DHAS_KONAMI=1 -DHAS_M68000=1 -DHAS_M68010=1 -DHAS_M68EC020=1 -DHAS_M68020=1 -DHAS_T11=1 -DHAS_S2650=1 -DHAS_TMS34010=1 -DHAS_TMS34020=1 -DHAS_TMS9900=0 -DHAS_TMS9940=0 -DHAS_TMS9980=1 -DHAS_TMS9985=0 -DHAS_TMS9989=0 -DHAS_TMS9995=1 -DHAS_TI990_10=0 -DHAS_TMS99105A=0 -DHAS_TMS99110A=0 -DHAS_Z8000=1 -DHAS_TMS32010=1 -DHAS_TMS32025=1 -DHAS_TMS32031=1 -DHAS_CCPU=1 -DHAS_PSXCPU=1 -DHAS_ASAP=1 -DHAS_UPD7810=1 -DHAS_UPD7807=1 -DHAS_ARM=1 -DHAS_JAGUAR=1 -DHAS_R3000=1 -DHAS_R4600=1 -DHAS_R5000=1 -DHAS_SH2=1 -DHAS_DSP32C=1 -DHAS_PIC16C54=0 -DHAS_PIC16C55=1 -DHAS_PIC16C56=0 -DHAS_PIC16C57=1 -DHAS_PIC16C58=0 -DHAS_G65816=1 -DHAS_SPC700=1 -DHAS_E132XS=1 -DHAS_CUSTOM=1 -DHAS_SAMPLES=1 -DHAS_DAC=1 -DHAS_DISCRETE=1 -DHAS_AY8910=1 -DHAS_YM2203=1 -DHAS_YM2151=0 -DHAS_YM2151_ALT=1 -DHAS_YM2608=1 -DHAS_YM2610=1 -DHAS_YM2610B=1 -DHAS_YM2612=1 -DHAS_YM3438=1 -DHAS_YM2413=1 -DHAS_YM3812=1 -DHAS_YM3526=1 -DHAS_YMZ280B=1 -DHAS_Y8950=1 -DHAS_SN76477=1 -DHAS_SN76496=1 -DHAS_POKEY=1 -DHAS_TIA=1 -DHAS_NES=1 -DHAS_ASTROCADE=1 -DHAS_NAMCO=1 -DHAS_NAMCONA=1 -DHAS_TMS36XX=1 -DHAS_TMS5110=1 -DHAS_TMS5220=1 -DHAS_VLM5030=1 -DHAS_ADPCM=1 -DHAS_OKIM6295=1 -DHAS_MSM5205=1 -DHAS_MSM5232=1 -DHAS_UPD7759=1 -DHAS_HC55516=1 -DHAS_K005289=1 -DHAS_K007232=1 -DHAS_K051649=1 -DHAS_K053260=1 -DHAS_K054539=1 -DHAS_SEGAPCM=1 -DHAS_RF5C68=1 -DHAS_CEM3394=1 -DHAS_C140=1 -DHAS_QSOUND=1 -DHAS_SAA1099=1 -DHAS_IREMGA20=1 -DHAS_ES5505=1 -DHAS_ES5506=1 -DHAS_BSMT2000=1 -DHAS_YMF262=1 -DHAS_YMF278B=1 -DHAS_GAELCO_CG1V=1 -DHAS_GAELCO_GAE1=1 -DHAS_X1_010=1 -DHAS_MULTIPCM=1 -DHAS_C6280=1 -DHAS_SP0250=1 -DHAS_SCSP=1 -DHAS_PSXSPU=1 -DHAS_YMF271=1 -DHAS_ICS2115=1 -O2 -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -ftree-vectorize -funsafe-math-optimizations -pipe -DGIT_VERSION=\"" 059806b"\" -fPIC -DRETRO_PROFILE=0 -Wall -Wno-sign-compare -Wunused -Wpointer-arith -Wbad-function-cast -Wcast-align -Waggregate-return -Wshadow -Wstrict-prototypes -Wformat-security -Wwrite-strings -Wdisabled-optimization -O2 -DNDEBUG -fomit-frame-pointer -fstrict-aliasing -Isrc -Isrc/includes -Isrc/cpu/m68000 -Isrc/libretro -Isrc/libretro/includes/zlib -Isrc/libretro/libretro-common/include -Isrc/libretro/libretro-common/include/file -Isrc/libretro/libretro-common/include/compat -Dstricmp=strcasecmp -fsigned-char -fPIC -c -osrc/libretro/libretro-common/file/file_path.o src/libretro/libretro-common/file/file_path.c
**src/libretro/libretro-common/file/file_path.c:34:30: fatal error: string/stdstring.h: No such file or directory**
#include <string/stdstring.h>
^
compilation terminated.

Not sure if this is enough information. Will keep investigating, but in the meantime, thought somebody here might have a better clue than me.

Thanks!
-Roslof

markwkidd

There are two issues.

You're seeing #1 in the log you posted. twinaphex and bparker from libretro are doing some intensive work on the build system for mame2003-plus and things are stalled right now while they figure something out.

#2 is that this PR (or something equivalent) needs to be added to RetroPie setup https://github.com/RetroPie/RetroPie-Setup/pull/2369

Summary: It may be a day or two before mame2003-plus compiles again, but it will probably be somewhat better than ever when it does.

roslof

Very helpful, markwkidd. Thank you for the fast response!
Will monitor/ follow-up on their github page.

Have a great night
-Roslof

markwkidd

Update: It looks like the libretro crew finished their work, so it's down to just issue #2 about the setup script.

markwkidd

One more update. Your build issue now affects standard mame2003 as well, so there is a new RetroPie-Setup PR to solve build issues for both versions of the core: https://github.com/RetroPie/RetroPie-Setup/pull/2370

markwkidd

The RetroPie-Setup PR was just merged, so @roslof you ought to be able to update RetroPie-Setup and then be able to build mame2003-plus. Please let me know if there are problems.

roslof

Thanks again markwkidd,

Good news is that the build gets much further (near the end) but eventually errors:

Could not successfully install Arcade emu - updated MAME 0.78 port for libretro with added game support (/home/pi/RetroPie-Setup/tmp/build/lr-mame2003-plus/changed.txt not found).

Feels like it's almost there. "lr-mame2003-plus" now appears in the emulator drop down list, but attempting to use it fails as expected.

Clearly, the team is working on this, so I'm not concerned. For fun, I might inject a dummy changed.txt at the location and see if this gets further along.

Best,
ros

markwkidd

I can't be sure but it sounds like you need to update your RetroPie setup script

mitu

@roslof Did you update the RetroPie setup script before re-compiling ? The file you mention has been removed from the package so you shouldn't get that error anymore if you updated.

roslof

Thanks guys. You're both right -- I hadn't updated the script. Will try again.

roslof

Of course, that worked like a charm.
Thank you for the support!