Linux Gaming

15911 readers

4 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago

MODERATORS

[email protected]

glibc and glibc-eac-bin are in conflict (Installed glibc-eac-bin for Insurgency Sandstorm) (self.linux_gaming)

submitted 3 months ago by promitheas to c/[email protected]

12 comments fedilink hide all child comments

Hello everybody! My brother plays Insurgency Sandstorm a lot and I wanted us to be able to play together, so I got it and after some messing about got it working on my system. One of the things I read in forum posts to do to get it to work on an Arch based system is to install glibc-eac-bin which has some patches to make certain games work (I hope I understood that correctly).

Today when I try to update my system I get the following message and it will not allow me to continue:

:: Starting full system upgrade...

resolving dependencies...

looking for conflicting packages...

:: glibc-2.40+r16+gaa533d58ff-1 and glibc-eac-bin-2.40-1 are in conflict. Remove glibc-eac-bin? [y/N]

I dont want to remove glibc, but i want the message to go away and to be able to proceed with my updates. Any suggestions on what I should do?

Thanks in advance

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 3 months ago (1 children)

Oh, thanks for looking it up. This sounds good and harmless.

Now it would be interesting to know if there's a legitimate need for this, or EAC just can't be bothered to fix their software.

[–] [email protected] 1 points 3 months ago

I'm not that knowledgeable, but I guess it's EAC's fault: Apparently every application known to mankind, that uses glibc, is compatible with (the better) GNU hashtables. Except EAC. It may just be some incompatibility out of their reach, but then I wonder why every other program, native or run via wine, does not have this problem. My guess: They discovered that they could quietly remove GNU hashtable support, and therefore annoy most linux users, while just saying "your stuff is not compatible with my perfectly fine program".