That message happens when a new binary is run on an old glibc, not the other way... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		floatboth on March 27, 2020 \| parent \| context \| favorite \| on: About Musl That message happens when a new binary is run on an old glibc, not the other way around.

ur-whale on March 27, 2020 [–]

Yes, you'd think so indeed.

Unfortunately, I've seen the exact opposite in production: older binary running atop newer glibc and crashing with that kind of message.

glibc abi compatibility is and has been a joke.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact