Trouble installing Mupen64 core

[grazzii]

Hi, I've had a search around the site and can't find a suitable answer to the issue I'm facing.

Raspberry Pi 4 (Official power supply) - aarch64
Running Debian / 12 Bookworm
build-essential is up to date
libpng-dev is up to date
Installed RetroPie along side my system using the bash script found in the documentation.

When trying to install Mupen64 core for RetroPIe, through the RetroPIe-Setup script, I had an error saying the aarch64 flag was not supported. Okay, I can understand that there may not be a source available for this system.

I then try the lr-mupen64plus-next package, as it didn't appear to have an issue with the flag. I unfortunatly get a build error relating to Glide64:

g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make: *** [Makefile:673: GLideN64/src/GlideNHQ/TextureFilters_hq4.o] Error 1

What's interesting is TextureFilters-hq2x.o was created in the previous step. Whilst the implementation of *hq2x.cpp and *hq4x.cpp are written very differently, perhaps there is logic in hq4x that is unsupported on my current architecture.

If this is indeed an issue with this particular filter, is there a way I can omit it from the build process? I've removed it from the CMakeLists.txt to see if that may help, but this might point to a wider incompatibility issue with my system.

Any thoughts on how best to proceed? Thanks :)

Update:
Even stranger, re-running this. It now fails 67 steps before, and failed to build opengl_Wrapper.o with the same error as above. Very confused what the issue can be here.
Just a blip :)

[mitu]

When trying to install Mupen64 core for RetroPIe, through the RetroPIe-Setup script, I had an error saying the aarch64 flag was not supported. Okay, I can understand that there may not be a source available for this system.

Yes, you're trying to build an old and un-maintained libretro core. The current up-to-date core is lr-mupen64plus-next, which is tested and works on 64bit ARM.
Leaving aside the fact that you're running on a not-yet supported OS release and the warning that 64bit is also in a beta state.

If this is indeed an issue with this particular filter, is there a way I can omit it from the build process? I've removed it from the CMakeLists.txt to see if that may help, but this might point to a wider incompatibility issue with my system.

That's a red herring and the file itself may not be the issue. Can you post the entire build log ?

[grazzii]

@mitu Thanks for your response!

Here's the pastebin with the log https://pastebin.com/TJ8rZ0wD (PW: EFSCbcCGHT )

As this is a fairly new installation, I could install Debian Bookworm 32-bit if that may solve these issues. This is going to be used 60% for gaming, 40% for desktop use so I'd rather have the most compatible system for RetroPie than 64-bit architecture. I didn't realise the OS wasn't supported yet - the official RPi Imager software highlights 64-Bit to be the recommended installation, but yes I did see the warning on configuration RetroPIe - I did brace myself for some incompatibility :)

[mitu]

How much RAM does your system have ?

I think the error is from not having enough RAM to compile the core (something similar to https://github.com/RetroPie/RetroPie-Setup/pull/3576). If you only have 1Gb, then using a 64bit system + desktop is going to be ... problematic. Add some extra swap memory (2Gb) and see if you can complete the compilation.

[grazzii]

@mitu Doh! What a simple fix. Yes I do have the 1GB model for this particular install. I increased the swap up to 2GB and the build went down absolutely fine.
Would installing the 32Bit system give better performance results in your opinion? Either way, N64 is now working absolutely fine. Thank you so much for your help!

[mitu]

@grazzii said in Trouble installing Mupen64 core:

Would installing the 32Bit system give better performance results in your opinion?

No, but it will consume less memory for the same tasks. You can stick with 64bit, but if you intend to use it also as a desktop computer then memory size may become an issue (regardless of the 32bit/64bit choice).