New comment by nonchip on void-packages repository

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

Comment:
@dexgs are we **sure** on that though? definitely not how i'd read @oreo639's last comment (or literally any of the others trying to compare/replace those) with the "verified that i built it the same and it doesn't work", and all @Johnnynator said was they "set up a chroot" without details as to *what* was setup *how*, and those usually contain more than just a single libc.

and we've already proven it's unrelated to the existence or absence or naming or format of DT_HASH sections, the thing everyone keeps blaming here for no reason whatsoever.

i'm not saying it can't be the glibc, but all the experimentation say it definitely can't be DT_HASH, and it most likely isn't anything else "meta" about it. so short of EAC parsing opcodes in glibc like some weirdo antivirus thing and shitting itself because we ran an optimizer slightly different or such, it sounds more likely to be at least not glibc's fault *alone*.