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=-3.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 18756 invoked from network); 23 Sep 2020 16:26:45 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 23 Sep 2020 16:26:45 -0000 Received: (qmail 10231 invoked by uid 550); 23 Sep 2020 16:26:40 -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 10184 invoked from network); 23 Sep 2020 16:26:39 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dereferenced.org; s=default; t=1600878388; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qTbNT6Hk7fBP6MP9gNKrXb2i9djs88+kvu2cCMYmaII=; b=ogk3DMQq741DnrHeQl4bMawRf12Qmg8jHq9TCWKIKCcKf1ahC+1hQWeSNqswsRDmPMH3md VA3AQqMvCa083HlZjDXIhHhUan0CoGUVJeXgweqXvRjItkltEAhCjEwUB5QRuqqbFyXGhs iYvrA2J+JKTfqe6gqt6sWC3swPZyNso= To: musl@lists.openwall.com, Jeffrey Walton References: <4768019.hHWyC0TzgU@omega> <20200920135629.GI2947641@port70.net> <20200920171446.GB3265@brightrain.aerifal.cx> <2533200.g9kxISXj3W@omega> <20200922184610.GI3265@brightrain.aerifal.cx> <20200923160824.GJ3265@brightrain.aerifal.cx> X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Ariadne Conill Message-ID: <7bd0a1a7-ffad-fd02-21a1-e4c6f0400146@dereferenced.org> Date: Wed, 23 Sep 2020 10:26:24 -0600 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [musl] Re: OS detection wrong on Alpine Linux 3.10 Hello, On 2020-09-23 10:16, Jeffrey Walton wrote: > On Wed, Sep 23, 2020 at 12:08 PM Rich Felker wrote: >> >> On Wed, Sep 23, 2020 at 09:13:16AM -0400, James Y Knight wrote: >>>> >>>>> All I need to know is what version of Musl I am dealing with and I can >>>>> configure myself. >>>> >>>> Are you willing to maintain an #ifdef forest for all the versions of >>>> all the libcs and all the kernels your programs may be used with, so >>>> you can list exhaustively the available features in every configuration? >>> >>> At the risk of jumping in on a question asked of someone else: yes, >>> absolutely! (Not _all_ available features of course, just the ones >>> required.) >>> >>> There are generally not that many nonstandard features you'd want to use in >>> a typical program, and using an ifdef forest to implement an abstraction >>> layer around those couple items is just fine. >> >> I can't know whether you're "willing", but you're definitely not >> willing and able. "All the..." includes people's personal projects >> (from scratch or patches to existing ones) that you will never see, >> future systems that come into existence long past your involvement in >> the project or even your lifetime, etc. > > Unless something has changed recently, Botan, Crypto++ and OpenSSL are > still being carried by most Linux distributions. OpenSSL is also > regularly distributed as part of other OSes, like AIX, Android, BSDs, > iOS, OS X and Solaris. > > And unlike some other projects,[1] Botan, Crypto++ and OpenSSL > actually work in practice on all the platforms without a configuration > program that performs feature tests. You are dead wrong on this topic. OpenSSL actually goes the other way and performs absolutely wacky tests like "are we running on big-endian amd64." Any cryptography library is going to have to perform feature tests (either at build time or run time) to determine whether features like hardware acceleration are possible. > [1] the Rust compiler comes to mind here. It works on Linux x86_64, > but it's hit or miss whether it works or not on other architectures > like ARMv7, Aarch64 and PowerPC, even after an approved configuration > program is run. Cargo is capable of doing build-time configuration tests. If a crate fails to properly run tests, it is not because the Rust ecosystem works as you believe it does. Ariadne