Re: strverscmp is buggy in newlib 4.4.0 (was Cygwin 3.4.6)

2024-01-04 Thread Brian Inglis via Cygwin
On 2024-01-02 10:36, Brian Inglis via Cygwin wrote: On 2024-01-02 03:23, Bruno Haible via Cygwin wrote: Here's a test case of strverscmp, from Dmitry Bogatov [1] #include int main () {    return strverscmp ("UNKNOWN", "2.2.0") <= 0; } It succeeds on glibc and musl libc 1.2.4, but fails on musl

Re: strverscmp is buggy in newlib 4.4.0 (was: Cygwin 3.4.6)

2024-01-02 Thread Brian Inglis via Cygwin
On 2024-01-02 13:29, matthew patton via Cygwin wrote: The cause is apparently that Cygwin's strverscmp implementation wasborrowed from musl libc would it make sense to use git submodules when "borrowing" code so the upstream reference is not lost, and keeping it abreast is relatively trivial

Re: strverscmp is buggy in newlib 4.4.0 (was: Cygwin 3.4.6)

2024-01-02 Thread Brian Inglis via Cygwin
On 2024-01-02 03:23, Bruno Haible via Cygwin wrote: Here's a test case of strverscmp, from Dmitry Bogatov [1] #include int main () { return strverscmp ("UNKNOWN", "2.2.0") <= 0; } It succeeds on glibc and musl libc 1.2.4, but fails on musl libc 1.2.3 and Cygwin 2.9.0 and 3.4.6. The cause is