The difference is that you can statically link GTK+, and it'll work. You can't s... | Hacker News

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

		JoshTriplett 2 days ago \| parent \| context \| favorite \| on: Loss32: Let's Build a Win32/Linux The difference is that you can statically link GTK+, and it'll work. You can't statically link glibc, if you want to be able to resolve hostnames or users, because of NSS modules.

viraptor 2 days ago [–]

Static linking itself doesn't prevent modules. There's https://github.com/pikhq/musl-nscd for example

JoshTriplett 2 days ago | [–]

Not inherently, but static linking to glibc will not get you there without substantial additional effort, and static linking to a non-glibc C library will by default get you an absence of NSS.

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