Arch Linux User Repository

@xiota Tried building the package from that git, didn't seem to fix the issue.

This package addresses only problems caused by absent DT_HASH. Some games have other problems. Patches at Frogging-Family/glibc-eac.

@MacTavishAO OpenSUSE seemed to have worked for me, additionally it works on the Steam Deck's current version of SteamOS. I can gift you the game if you want.

Updated to latest official PKGBUILD and set TIMEOUTFACTOR to prevent false testing failures on slower systems and network conditions.

@MaKaNu please try rebuilding now. If you're confident it's a false positive, you can try passing --nocheck to makepkg.

@cncz Unfortunately, I cannot provide debugging symbols through debuginfod.archlinux.org as this is not an official package. You need to build this package with debug enabled. Take a look here: https://wiki.archlinux.org/title/Debugging/Getting_traces#Rebuilding_packages

@markmann I have no way to test your claim as I don't own that game and I couldn't find any information online from Linux users apart from 2 unhelpful protondb posts. If you know of any distro that can run this game please tell me so I can take a look at their glibc building process to see if I can figure it out.

Doesn't work with newer games such as Megaton Musashi W. Is there a repository or an email where I can report these issues?

This seems to break the debuginfo for any applications that use libc functions, valgrind will spit the following error when doing a leak check on a program using strcmp:

valgrind:  Fatal error at startup: a function redirection
valgrind:  which is mandatory for this platform-tool combination
valgrind:  cannot be set up.  Details of the redirection are:
valgrind:  
valgrind:  A must-be-redirected function
valgrind:  whose name matches the pattern:      strcmp
valgrind:  in an object with soname matching:   ld-linux-x86-64.so.2
valgrind:  was not found whilst processing
valgrind:  symbols from the object with soname: ld-linux-x86-64.so.2
valgrind:  
valgrind:  Possible fixes: (1, short term): install glibc's debuginfo
valgrind:  package on this machine.  (2, longer term): ask the packagers
valgrind:  for your Linux distribution to please in future ship a non-
valgrind:  stripped ld.so (or whatever the dynamic linker .so is called)
valgrind:  that exports the above-named function using the standard
valgrind:  calling conventions for this platform.  The package you need
valgrind:  to install for fix (1) is called
valgrind:  
valgrind:    On Debian, Ubuntu:                 libc6-dbg
valgrind:    On SuSE, openSuSE, Fedora, RHEL:   glibc-debuginfo
valgrind:  
valgrind:  Note that if you are debugging a 32 bit process on a
valgrind:  64 bit system, you will need a corresponding 32 bit debuginfo
valgrind:  package (e.g. libc6-dbg:i386).
valgrind:  
valgrind:  Cannot continue -- exiting now.  Sorry.

Why does it fail to build?

I have a lot of UNSUPPORTED following two failed checks:

FAIL: misc/tst-preadvwritev2
FAIL: misc/tst-preadvwritev64v2

What might be the issue?

Having this error after update... ==> Cleaning up... [sudo] password for ramazotti: loading packages... resolving dependencies... looking for conflicting packages... :: glibc-eac-2.39-4 and glibc-2.39+r52+gf8e4623421-1 are in conflict. Remove glibc? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: removing glibc breaks dependency 'glibc=2.39+r52+gf8e4623421' required by lib32-glibc -> error installing: [/home/ramazotti/.cache/yay/glibc-eac/glibc-eac-2.39-4-x86_64.pkg.tar.zst] - exit status 1

I'm stupid, I wont delete this but post the solution. Just yay -S lib32-glibc-eac

It should work now.