Package Details: lib32-glibc-eac 2.40-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.159863
First Submitted: 2024-02-07 00:41 (UTC)
Last Updated: 2024-07-25 05:04 (UTC)

Dependencies (5)

Required by (598)

Sources (7)

Latest Comments

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

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?

Ramazottii commented on 2024-05-14 10:19 (UTC) (edited on 2024-05-14 10:29 (UTC) by Ramazottii)

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

MacTavishAO commented on 2024-05-03 21:14 (UTC)

It should work now.

Tebro commented on 2024-05-01 07:55 (UTC) (edited on 2024-05-01 07:55 (UTC) by Tebro)

I am trying to build this (with yay first, but also chroot) and I get this failure

<command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
<command-line>: note: this is the location of the previous definition
cc1: all warnings being treated as errors
make[2]: *** [../o-iterator.mk:9: /build/glibc-eac/src/glibc-build/stdlib/testmb.o] Error 1
make[2]: Leaving directory '/build/glibc-eac/src/glibc/stdlib'
make[1]: *** [Makefile:484: stdlib/tests] Error 2
make[1]: Leaving directory '/build/glibc-eac/src/glibc'
make: *** [Makefile:9: check] Error 2
==> ERROR: A failure occurred in check().

xiota commented on 2024-04-27 11:55 (UTC)

Try building in a clean chroot.

If that doesn't work, something may be wrong with the patch.

konradmoesch commented on 2024-04-27 11:41 (UTC) (edited on 2024-04-27 11:44 (UTC) by konradmoesch)

With ld I get: configure: error: --enable-multi-arch support requires assembler and linker support, with lld I also get

ld.lld: warning: unknown -z value: nomark-plt
ld.lld: error: version script assignment of 'GLIBC_2.4' to symbol '__stack_chk_guard' failed: symbol not defined
ld.lld: error: version script assignment of 'GLIBC_PRIVATE' to symbol '__nptl_set_robust_list_avail' failed: symbol not defined
ld.lld: error: version script assignment of 'GLIBC_PRIVATE' to symbol '__pointer_chk_guard' failed: symbol not defined
ld.lld: error: version script assignment of 'GLIBC_PRIVATE' to symbol '_dl_make_stack_executable' failed: symbol not defined
ld.lld: error: version script assignment of 'GLIBC_PRIVATE' to symbol '_dl_starting_up' failed: symbol not defined

So, which linker should I use to make this pkg?