X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D24AC3858413 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1672781612; bh=bdrASC8+KCOl2R9rMYgYc45hGuuuZYeqgF8kUoZyvrA=; h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=qqqI6TRnOI0lSsnZHH3VqH1diwo68+5Kn058VLVFJI9wL5yUmtydPO/T9Yhcz61c1 zXf5aKWppC8EJiYz06Z5GxjV3Ub1D6DCza0YzCHtWwUjZ8Nw71JQLD06tTioCKtoqX pJAcFjkC13aTAZ7iPzh46zQ5YEiopPtKFOi/vuv0= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com Message-ID: <6cb9660a-1273-1790-4cee-c445597d1798@emmenlauer.de> Date: Tue, 3 Jan 2023 22:33:14 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 To: cygwin AT cygwin DOT com Content-Language: en-US X-SA-Exim-Connect-IP: 77.24.102.157 X-SA-Exim-Mail-From: mario AT emmenlauer DOT de X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_INFOUSMEBIZ, SPF_HELO_NONE, TXREP, T_SPF_PERMERROR autolearn=no autolearn_force=no version=3.4.6 Subject: Kind request to update 'nasm' X-SA-Exim-Version: 4.2.1 (built Sat, 08 Feb 2020 21:53:50 +0000) X-SA-Exim-Scanned: Yes (on aldebaran.he1ix.org) X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Mario Emmenlauer via Cygwin Reply-To: Mario Emmenlauer Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 303LXuLx013594 Dear All, the current version of OpenSSL (1.1.1s) fails to build for me with an error in nasm. The issue is reported upstream and supposedly fixed already, see https://bugzilla.nasm.us/show_bug.cgi?id=3392658 I've tested nasm 2.16.1 from the upstream win32 builds and it does indeed fix the problem. However I would prefer a Cygwin deployment over manually maintained archives. Could someone kindly consider updating 'nasm' to current latest 2.16, or anything including or higher than 2.15.01? All the best, Mario Emmenlauer -- BioDataAnalysis GmbH, Mario Emmenlauer Tel. Buero: +49-89-74677203 Balanstr. 43 mailto: memmenlauer * biodataanalysis.de D-81669 München http://www.biodataanalysis.de/ -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple