"We HAVE to link libc dynamically so we can fix bugs centrally!" <5 years later> everything is VMs <5 years later> containers in VMs
-
-
Replying to @rygorous
also somewhere in the middle of that we fucking broke binary compatibility of memcpy to slightly improve perf on f**king Intel Atom.
3 replies 15 retweets 70 likes -
-
Replying to @11rcombs
Act 1: https://bugzilla.redhat.com/show_bug.cgi?id=638477 … - a bug in app code at that point, but that change broke enough SW that it probably should've been reverted.
2 replies 1 retweet 12 likes -
Act 2: glibc uses symbol versioning so that apps compiled against newer glibcs get the new behavior, old apps keep old behavior.
1 reply 1 retweet 4 likes -
Which sounds fine in principle, since that's what symbol versioning is for, but: Act 3: therefore, anything compiled on a machine with a
2 replies 1 retweet 5 likes
Symbol versioning is just an utter shit show. It doesn't do what it's intended or expected by users to do, & makes huge ver-dep problems.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.