Re:RipGrep musl binaries occasionally segfault during very-l...
by inigyou on Sunday August 02, 2026 @05:05AM
(#49142560)
Yeah we could all just use glibc. You see the problem with that though right?
[ Parent
| on HN ]
Re:RipGrep musl binaries occasionally segfault during very-l...
by fc417fc802 on Sunday August 02, 2026 @10:45AM
(#49145146)
That isn't at all what I said. I'm pointing out that in reality there aren't 20 competing libc implementations each with a unique dynamic linking scheme used by the userspace of 20 corresponding linux distributions. Instead we have ... glibc. So if the kernel actually specified a common portable linking scheme to fall back on as a means to interface with critical drivers it would presumably adopt the glibc way of doing things for that purpose.
Also I did not say "just use glibc" but rather suggested to just include a secondary glibc compatible dlopen routine. Exactly as you would have to do if the kernel bothered to specify.
Re:RipGrep musl binaries occasionally segfault during very-l...
by inigyou on Sunday August 02, 2026 @10:50AM
(#49145191)
If the kernel wanted to force you to use glibc it would do so. We could get rid of the stupid hardcoded paths in PT_INTERP for example.
Re:RipGrep musl binaries occasionally segfault during very-l...
by fc417fc802 on Sunday August 02, 2026 @10:57AM
(#49145255)
Right. Obviously. What I'm pointing out is that if the kernel decided to include dynamically linking to certain drivers within its scope (which it does not wish to do at present as you rightly point out) then it would need to specify a scheme for doing so. At which point glibc is all but a foregone conclusion.
So just pretend they did that and include a second dlopen routine and get on with life because at that point you're compatible with ~all major linux distros.
Far more pressing is a blessed filesystem path for where to find the things.