ScummVM not building on Zero2

ParadoxGBB

Hey all,

The binary for the SDL2 version appears to be about a year old and I wanted to try with some of the newer engines. There are performance issues with lr-scummvm, so I'm sticking with regular scummvm for now.

I'm hitting the following build error --- anyone else hitting this? Just me?

(Entire log too big for pastebin, sorry)

C++      graphics/scaler/tv.o
    C++      graphics/scaler/hq.o
g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make: *** [Makefile.common:171: graphics/scaler/hq.o] Error 1
strip: '/home/pi/RetroPie-Setup/tmp/build/scummvm/scummvm': No such file
Could not successfully build scummvm - ScummVM (/home/pi/RetroPie-Setup/tmp/build/scummvm/scummvm not found).
/home/pi

Log ended at: Wed 22 Feb 13:56:43 PST 2023
Total running time: 5 hours, 17 mins, 51 secs

mitu

Looks like not enough memory. If you have EmulationStation running, stop it first and then try installing again.

ParadoxGBB

@mitu Thanks so much for the help, but unfortunately hit the same error. It takes over 4 hours per attempt. I think you're on the right track, had no problem with my Pi4.

Maybe I can try building on my Pi3 and transferring it to my Zero2...

Looking closer at the scriptmodule but it looks like the head command for the repro even when building from source gets you also to January 2022, right after 2.5.1. The build reports 2.6.0 but it's substantially before the 8/22 release of 2.6.0.

Just curious if anyone is aware why this is set up this way? If I'm understanding this correctly there's no advantage from building without editing the head, which I was going to try if this succeeded --- wouldn't most folks assume that building from source would be either latest release or latest repro? Understood that from a quality perspective that might be harder to support from RetroPie's end...

mitu

@ParadoxGBB said in ScummVM not building on Zero2:

Just curious if anyone is aware why this is set up this way?

There was a bug in the 2.5.1 release, fixed after that release, that affected the older Pi models. It was shortly fixed in the upcoming 2.6.x release cycle, hence the usage of a particular commit and not a straight release tag. git blame should have more details.

You can add more swap memory just for the build or wait for the upcoming 2.7.0 release, which will be added in RetroPie soon and you can install from a binary package.

ParadoxGBB

Thanks! I'll wait.