PPSSPP fails to build from source on x86_64 system

mitu

@movisman This is an upstream issue, from what I've seen in the forums (and also on reddit), PPSSPP is undergoing a lot of changes and the master branch is quite experimental. Unfortunately for your case, there is no binary installation option, so you can try an find an older version already compiled - see http://www.noobslab.com/2017/01/ppsspp-psp-emulator-130-version.html for a PPA repo with a stable version.

movisman

@mitu

Hi there,

Thanks a lot for the info, I appreciate it.

Do you know what would be the best way to integrate the install into retropie after installing the binaries separately? Basically the usual stuff which is at the end of the PPSSPP.sh script where directories are created, configs are moved, and system entries are put in etc.

Am I best off making a copy of that script, removing the build portion of the file and running it to do the other bits post-install?

Cheers

psyke83

The easiest way would be to edit scriptmodules/emulators/ppsspp.sh and add a release tag to the git repo. For example, to checkout the v1.5.3 tag:

    gitPullOrClone "$md_build/ppsspp" https://github.com/hrydgard/ppsspp.git v1.5.3

Note that I can't guarantee which tagged build will compile correctly, so you'll need to decide which tag to try: https://github.com/hrydgard/ppsspp/releases

Try building from source again (making sure to clear the existing source folder beforehand). Don't forget to restore ppsspp.sh to defaults when you're finished so that it won't break future script updates:

$ cd RetroPie-Setup
$ git checkout scriptmodules/emulators/ppsspp.sh

BuZz

@movisman ~~Please post full logs when reporting issues - via pastebin.com or similar . the errors are further up in the output.~~ Sorry - I missed the link before the snippet - will check your full log.

From my test just now it looks related to SDL/wayland code.

I have rolled back to the last working version.

psyke83

The 1.5.4 release may have stability issues on Raspberry Pi due to this commit: https://github.com/hrydgard/ppsspp/commit/4b59fe6daca86c3efb1abdfa527099850b33751c

It causes a build failure on stretch, but for the current RetroPie images it may cause instability on jessie due to libEGL and libbrcmEGL being mixed together. It was fixed by https://github.com/hrydgard/ppsspp/commit/20080ba1236c8bff21b74d47235fd7a302af49fd

BuZz

@psyke83 thanks. The last RPI bin should be fine though. However feel free to fix this :-)

psyke83

It is fixed :). The problem is we can't control the frequency or timing by which upstream tags releases, so having better version control would be helpful... pokes

The latest problem with master is this: https://github.com/hrydgard/ppsspp/issues/10458

Still working on isolating when the problem was introduced, as there have been a lot of failed builds for Pi in that commit range.

BuZz

@psyke83 I meant to fix the problem you mentioned for v1.5.4 on retropie (eg with a patch) (since we can't use master for other reasons).

If you think v1.5.4 will be problematic with the mixed lib names (or we can wait and see if people report issues).

movisman

@buzz @psyke83

Hi both,

Thanks for your help with this. I have just got round to reinstalling from source and this time it seemed to build correctly this time. I haven't tested the emulator yet but will do so shortly.

Cheers

movisman

@buzz @psyke83

Hi,

PPSSPP has been working really well on my x86 machine, but I was wondering, are you able to revert this change yet so it grabs the latest build:
https://github.com/RetroPie/RetroPie-Setup/commit/4852d12c8a9b8cc75e110dc450ea8aef1e6c57a1

As I wouldn't mind trying out the Vulkan driver, which I cannot seem to select at the mo. I think that might be due to the version it downloads using the setup script. Otherwise, I can always download it separately to check it out.

Cheers

BuZz

@movisman as I mentioned on github, there are issues with master currently and I may well stick to release tags.

movisman

@buzz

Yep completely understood, and that makes sense for the sake of keeping the releases as stable as possible. If I have time to test the Vulkan driver out I can always try to build from the master myself if there hasn't been a new release when I get round to it.

Thanks for the help as always.

Cheers