New comment by nonchip on void-packages repository

https://github.com/void-linux/void-packages/issues/41388#issuecomment-1909937322

Comment:
@nekopsykose thanks for your insight, my current best bet is on `.gnu.version_r` if i had to pick one, because it's very much **not** optional according to LSB (the way i understand the blogpost you linked to it's optional for "a libc" to have+support it, but glibc seems to *usually* have and its linker *does* support it) so there's a decent chance a "reasonable person" (and even an unreasonable ~~malware~~*anticheat* developer) might expect it. but like you say it might well not be any section difference, i just wanted to list them "for the record". i could just as likely see EAC accidentally triggering on some weird optimizer difference resulting in "suspicious" codegen or such :'D

@oreo639 i know you already did some tests, but you didn't show the details, and a lot of various quality levels of info are around on the googles about this topic, so i figured it doesn't hurt to start collecting some "hard facts" from some known good/bad samples, to make sure we're on a similar page to rule out or home in on the potential causes. (also offtopic but gotta love that "no-plt" means "use a different kind of plt")

> swapping the libc after launching steam didn't affect anything until restarting steam as opposed to the .hash checks which are performed when launching the game.

wait, am i reading that wrong or does that mean EAC does something to the libc *linking steam itself* instead of the game?