I've never tried before to install 2016 before yesterday. I just recently finished getting the matching romset and wanted to give it a go.
I'm reading the PR and I see there is a potential fix but it hasn't been incorporated into libretro if I'm reading this right. I'll see if I can work out how the fix can be incorporated but I'm still learning the terminology workings of github.
@windale You can use the module from the PR on github.
Thanks, the script works great. Feel free to add it. Although wouldn't it be better as separate scripts per core instead of force installing all of them and increasing the source install time ? I suppose up-to-date binaries would be OK.
Oh, there was a weird report on our discord saying that retropie only had .44 available some time ago (i told the guy to write a report here), so the issue was only about the build script description being outdated ?
PS : between new supported games and redumps, there should be around 2 dozens of romsets that changed since 126.96.36.199
@GongStar the output of dmesg might be useful after the build fails. You are right there is nothing else in the log - I thought there might be something. Not sure of the issue if you have plenty of free space on card, and no overclock.
You could rename the folder /opt/retropie/emulators/ppssppto something else and then modify the /opt/retropie/configs/psp/emulators.cfg and make a new entry for your copy. Retropie will ignore it then and won't touch it.
@funkotron77 Again, I see nothing. Maybe also check the /var/log/syslog, but without grep to see every message. A simple cat /var/log/syslog will show it, and you could copy & paste the last part of the output. To be sure, you could look at it before and after the remount command, to check for changes (the same goes for dmesg).
After that, alas, I'm out of ideas. I never had to deal with something similar myself yet.
Is there an lr-mame core? Could I build one? I have used lr-mess both prebuilt and built from source and I see from its build script that it just pulls from https://github.com/libretro/mame.git.
Yes. Both lr-mess and lr-mame are built from the same codebase you mentioned (forked upstream MAME), but with different build options, which results in different supported systems (arcade vs. non-arcade).
I was referring to MAME (the upstream project), not the libretro cores.
Does this mean that mame itself is the part of the mame distribution that can run that system?
Upstream MAME distributes only 1 binary which supports all systems included - either arcade, computer, mechanical, etc. There's no separate MESS anymore and I think hasn't been for quite some time.
Then it might be something with the latest update. I tried to test the libretro builbot version, but for some reason, the armv7-neon-hf build for the lr-mame core is build for aarch64 and it can't be used on RetroPie.
You can copy the drastic.sh version from that repo to your own RetroPie-Setup installation (overwriting $HOME/RetroPie-Setup/scriptmodules/emulators/drastic.sh) and then re-install drastic.
Do note that replacing the scriptmodule with another version will make updating the RetroPie-Setup fail, since you modified the file locally.