Package Details: lib32-glibc-eac 2.42+r3+gbc13db739377-1

Git Clone URL: https://aur.archlinux.org/glibc-eac.git (read-only, click to copy)
Package Base: glibc-eac
Description: GNU C Library (32-bit) with DT_HASH patch for games using EAC
Upstream URL: https://www.gnu.org/software/libc
Licenses: GPL-2.0-or-later, LGPL-2.1-or-later
Conflicts: lib32-glibc
Provides: lib32-glibc
Submitter: MacTavishAO
Maintainer: MacTavishAO
Last Packager: MacTavishAO
Votes: 13
Popularity: 0.000005
First Submitted: 2024-02-07 00:41 (UTC)
Last Updated: 2025-08-07 10:49 (UTC)

Dependencies (5)

Required by (853)

Sources (7)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

MacTavishAO commented on 2024-05-24 05:20 (UTC) (edited on 2024-05-24 05:26 (UTC) by MacTavishAO)

I can't reproduce these issues as packages build fine on my system. Could you paste tst-preadvwritev2.out and preadvwritev64v2.out to a gist website and share with me so I can take a look?

You can also try passing "--nocheck" to makepkg.

Could unstable overclocking/undervolting be at play here?

E_D3V commented on 2024-05-24 04:05 (UTC)

I have the same issue as @MaKaNu

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

markmann commented on 2024-05-21 17:39 (UTC)

Apologies, it seems like the recent switch to Wayland fixed the issue.

markmann commented on 2024-05-21 10:34 (UTC) (edited on 2024-05-21 10:36 (UTC) by markmann)

@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.

MacTavishAO commented on 2024-05-21 07:13 (UTC) (edited on 2024-05-21 07:13 (UTC) by MacTavishAO)

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.

markmann commented on 2024-05-21 02:37 (UTC)

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

cncz commented on 2024-05-20 05:30 (UTC) (edited on 2024-05-20 05:31 (UTC) by cncz)

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.

MaKaNu commented on 2024-05-18 19:51 (UTC) (edited on 2024-05-18 19:51 (UTC) by MaKaNu)

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?

« First ‹ Previous 1 2 3 4 5 Next › Last »