> Just dynamically link against the oldest glibc you want to support
replyI wish it would that simple for practical use cases.
I ship professional software for colorists for Hollywood studios and they absolutely love to never upgrade. We have to ship for RockyLinux 8. Sad.
RockyLinux doesn't sound so bad. It's not even EOL.
replyIt's just this short of being EOL.
replyAlmost three years?
reply>Rocky Linux 8 is supported by the Rocky Linux project until May 2029.
Yes but only the very last version and only paid support. Don't mind to pay, it's just that no amount of payment would be a proper solution to ancient environment with everything.
replyThis is not a desirable solution on musl based systems. Whatever you do in that situation ends up horrible, so it is about finding the least bad solution. Which this seems like a workable variant of.
reply> Just dynamically link against the oldest glibc you want to support.
replyJust the other day I tried running an older binary and it failed with a glibc error, despite it being linked to a glibc version that's barely 5 releases behind the one on my system. So maybe glibc isn't backwards compatible after all...