5 ms·
Software compiled against glibc links to versioned symbols, which are backwards compatible in ABI and behavior. I'm unsure of the reason you experienced breakin
by vortico 7y ago
Software compiled against glibc links to versioned symbols, which are backwards compatible in ABI and behavior. I'm unsure of the reason you experienced breaking software when upgrading your glibc version.
- mort96 7y agoThe GNU software which broke just didn't compile (with no upstream fix available for a long time, which I found incredible; I had to go find arch linux' repos' patch and apply that whenever I wanted to compile GNU build tools). The electron thing was apparently an LLVM linker thing according to your sibling comment. EDIT: the m4 patch in question: https://git.archlinux.org/svntogit/packages.git/tree/trunk/m4-1.4.18-glibc-change-work-around.patch?h=packages/m4 https://git.archlinux.org/svntogit/packages.git/tree/trunk/m... - apparently they still use it.
- shakna 7y ago> FIXME: Do not rely on glibc internals. Seems that's less of a glibc breaking compatibility, and more developers relying on something outside of the guaranteed API.
- mort96 7y agoI mean, it's GNU M4. It's at the core of GNU's build system. It's GNU developers depending on glibc internals. I'd be with you if it was just some random project, but it's pretty bad of an update to glibc to break the GNU toolchain.