On Tue, 16 Apr 2024 14:43:00 -0600, Lance Fredrickson <lancethepa...@gmail.com> 
wrote:

> Seeing the changes for aarch64 and vdso reminded me to ask, what's the
> current state of aarch64 and uclibc-ng? Last I checked in August 2022 it
> was still critically broken. These were some of the relevant emails I
> found at the time.
>
> https://www.mail-archive.com/devel@uclibc-ng.org/msg00953.html
> https://www.mail-archive.com/devel@uclibc-ng.org/msg00871.html

The ntpd/res_init problem should be fixed by "libc/inet/resolv: fix per thread
res_state access" [1] (and "fix compile for Linuxthreads enabled" [2])...

Regards,
Peter

[1] 
https://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/?id=67918f2bc3c4794d6d7e824963e5e0002d2ef10c
[2] 
https://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/?id=5b89fd74e7e9075049f3268424ab1ee14f811b0d

>
> thanks,
> Lance
> _______________________________________________
> devel mailing list -- devel@uclibc-ng.org
> To unsubscribe send an email to devel-le...@uclibc-ng.org

_______________________________________________
devel mailing list -- devel@uclibc-ng.org
To unsubscribe send an email to devel-le...@uclibc-ng.org

Reply via email to