Yo Alex! On Tue, 12 Apr 2022 16:56:20 -0400 "Alex Xu (Hello71)" wrote: > The issue of GNU-specific strerror_r has been discussed several times > on the mailing list: https://inbox.vuxu.org/musl/?q=strerror_r. See: > > - > https://inbox.vuxu.org/musl/20130208185918.GJ20323@brightrain.aerifal.cx/ > - > https://inbox.vuxu.org/musl/20180805010455.GQ1392@brightrain.aerifal.cx/ > > and other threads. The one suggests strerror_l(), which is uselsss for obvious reasons: strerror_l() strerror_l() is like strerror(), but maps errnum to a locale-dependent error message in the locale specified by locale. The behavior of str‐ error_l() is undefined if locale is the special locale object LC_GLOBAL_LOCALE or is not a valid locale object handle. I'm not going to ever use a function that in many (most?) cases has "behavior... undefined". gpsd, finally, solved the problem, by creating a configure test for the unexpected and undocumented behaviour of strerror_r() in musl. The other trhead says: > Is this a bug in musl? No, musl explicitly does not suppore the GNU interfaces that conflict with standard interfaces by the same name. After looking all over the musl source and doc, I can strongly assert that whatever is "explicitly" statad is very, very, hard to find. RGDS GARY --------------------------------------------------------------------------- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 gem@rellim.com Tel:+1 541 382 8588 Veritas liberabit vos. -- Quid est veritas? "If you can't measure it, you can't improve it." - Lord Kelvin