From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30526 invoked from network); 6 Nov 2022 23:24:28 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 6 Nov 2022 23:24:28 -0000 Received: (qmail 23789 invoked by uid 550); 6 Nov 2022 23:24:24 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 21702 invoked from network); 6 Nov 2022 23:18:41 -0000 Date: Sun, 6 Nov 2022 18:18:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kaction.cc; s=key1; t=1667776709; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=DM3rrfe4Kb+vn7I/2vrPEVQHS5yBRFaKwAMEHuMjO2c=; b=T4XI3A7tMB4PIeKjqukYvpZj5jH8RlvP202X/OhFGD+vd0Sg1WMQUmtF7W8nHfYO+QYXAh hnSaMOXxo34RjCUDsVNA5x1SFk0MAQDJ7xOxqwe4TJXw9teJumTewKI0lJ94js2GMAKf2h dVaeiI1uBwZaK9x7D95JoWv2RS/xHQA/Ljhr2+sItsd+JOGublhCjlM2JhxBknEEy8J15u oLppM40AoIC9PNA8vvYaDGHjyV5e2gQFDgqmBgRn7+XqgUgHByU7n0haXIqas8D+oWD9VI 4PwiLXL/yBRQAVa3gH+ZN+1+C/Niyf1XXzDX9g/gx3Tx5P/fQ8EG7u5wG9JPQA== To: bug-gsasl@gnu.org, musl@lists.openwall.com Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Dmitry Bogatov X-Migadu-Flow: FLOW_OUT Subject: [musl] Behaviour of strverscmp(3) Hello. While trying to building gsasl statically with musl library as part of Nixpkgs distribution, I noticed that test built from tests/version.c fails when built with musl library. After a bit of troubleshooting, I can pinpoint the reason -- different behaviour of "strverscmp" from glibc and musl. Example code: #include #include int main() { int value = strverscmp("UNKNOWN", "2.2.0"); printf("%d\n", value); return 0; } Under glibc value "35" is printed (positive), under musl value "-1" is printed (negative). Not sure what is the correct solution for the issue, so I cross-post into two lists. For now I plan to patch-out this particular test. Thank you.