Re: Experimental musl Port for FreeBSD

Konstantin Belousov <[email protected]> Sun, 26 Jul 2026 23:37:06 +0300
Newsgroups gmane.os.freebsd.devel.hackers
Message-ID <[email protected]>
On Sun, Jul 26, 2026 at 11:42:44PM +0800, ShengYi Hung wrote:
> For me, having another libc implementation would make it easier to perform
> A/B testing when debugging LLVM components (such as compiler-rt, LLDB, and
> other tools) on FreeBSD. I have also seen people test libm precision across
> multiple platforms with different libc implementations. In this case, having
> another libc implementation can help determine whether an issue is specific
> to FreeBSD or not.
> 
> Additionally, some users may want to build their own userspace with a
> different libc. Since the libc interface is relatively stable, I think it is
> worthwhile to spend some time porting another libc implementation to
> FreeBSD. If this project gains enough interest, I am willing to rewrite the
> AI-generated patch myself and work toward getting it merged upstream.
> 
> Regarding the musl libc AI policy, my understanding is that they do not
> accept AI-generated patches. I also do not feel comfortable submitting
> AI-generated patches to a project that I am not familiar with, so I will not
> do that.

More libc's the better, IMO.

I am very amused and happy to see the port rewritten properly
and upstreamed.

But remember the glibc where the port to FreeBSD existed and then rotten.
The description of glibc as portable gives very special meaning to
the word.