You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. It's "the Season", and I'm trying to keep myself entertained with fundamental questions.
The question of today is: why a curl-linux-x86_64-glibc is needed? At first, I thought that in case of glibc, it was not statically linked with glibc but only dynamically linked (on a old system to provide binary compatibility) to avoid the NSS problem mentioned in the README (btw this is what ChatGPT told me... :/)
But it seems that indeed glibc is statically linked into the binary.
Then why it is? Wouldn't the musl variant cover also glibc based systems without the NSS problem? Performance reasons?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello. It's "the Season", and I'm trying to keep myself entertained with fundamental questions.
The question of today is: why a
curl-linux-x86_64-glibcis needed? At first, I thought that in case ofglibc, it was not statically linked withglibcbut only dynamically linked (on a old system to provide binary compatibility) to avoid the NSS problem mentioned in the README (btw this is what ChatGPT told me... :/)But it seems that indeed
glibcis statically linked into the binary.Then why it is? Wouldn't the
muslvariant cover alsoglibcbased systems without the NSS problem? Performance reasons?Beta Was this translation helpful? Give feedback.
All reactions