19 points | by 1vuio0pswjnm7 7 hours ago ago
6 comments
I think my headline parsing has forever been ruined since I thought for sure someone created a 313 million parameter cross compiling fine tune
After opening the linked page, I still don't have any idea what the number is in the headline, nor why it's important
Three hundred and thirteen-point-three megabytes is how I parsed it, but I'm not sure of the significance of that either.
GCC toolchain glibc-linked binaries with musl libraries and headers, including musl dynamic loader
Out of the glibc tarpit
> including musl dynamic loader
Does this mean useful interfaces like PAM and nsswitch work on musl now?
> glibc-linked binaries with musl libraries
Why have any glibc? GCC et al. work fine compiled against musl (as proven by ex. Alpine only doing musl). Or is it for running on GNU/Linux systems (can't you statically link the build chain?)?
What's different from https://toolchains.bootlin.com/ ?
Or using Zig?
I think my headline parsing has forever been ruined since I thought for sure someone created a 313 million parameter cross compiling fine tune
After opening the linked page, I still don't have any idea what the number is in the headline, nor why it's important
Three hundred and thirteen-point-three megabytes is how I parsed it, but I'm not sure of the significance of that either.
GCC toolchain glibc-linked binaries with musl libraries and headers, including musl dynamic loader
Out of the glibc tarpit
> including musl dynamic loader
Does this mean useful interfaces like PAM and nsswitch work on musl now?
> glibc-linked binaries with musl libraries
Why have any glibc? GCC et al. work fine compiled against musl (as proven by ex. Alpine only doing musl). Or is it for running on GNU/Linux systems (can't you statically link the build chain?)?
What's different from https://toolchains.bootlin.com/ ?
Or using Zig?