From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 659BBC433EF for ; Wed, 6 Apr 2022 21:14:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235579AbiDFVQn (ORCPT ); Wed, 6 Apr 2022 17:16:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33554 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235394AbiDFVQH (ORCPT ); Wed, 6 Apr 2022 17:16:07 -0400 Received: from elephants.elehost.com (elephants.elehost.com [216.66.27.132]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CCE6C62D6 for ; Wed, 6 Apr 2022 13:01:16 -0700 (PDT) Received: from Mazikeen (cpe788df74d2cc1-cm788df74d2cc0.cpe.net.cable.rogers.com [72.138.27.250] (may be forged)) (authenticated bits=0) by elephants.elehost.com (8.16.1/8.16.1) with ESMTPSA id 236K1ErE051603 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Apr 2022 16:01:14 -0400 (EDT) (envelope-from rsbecker@nexbridge.com) Reply-To: From: To: "'Junio C Hamano'" Cc: "'Git Mailing List'" , References: <034101d84873$993f96f0$cbbec4d0$@nexbridge.com> <034701d84875$030bfb40$0923f1c0$@nexbridge.com> In-Reply-To: Subject: RE: [ANNOUNCE] Git v2.36.0-rc0 - Build failure on NonStops Date: Wed, 6 Apr 2022 16:01:08 -0400 Organization: Nexbridge Inc. Message-ID: <047c01d849f1$1192a9c0$34b7fd40$@nexbridge.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQE87yXqDmaysdJkpyH6/spM26GbOgJ005kMAt5RIzwBs7vyta3hw0vQ Content-Language: en-ca Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On April 6, 2022 12:14 PM, Junio C Hamano wrote: > writes: > >> On April 4, 2022 6:33 PM, Junio C Hamano wrote: >>>To: Randall S. Becker >>>Cc: Git Mailing List ; >>>git-packagers@googlegroups.com >>>Subject: Re: [ANNOUNCE] Git v2.36.0-rc0 - Build failure on NonStops >>> >>>CSPRNG_METHOD? >> >> We already have >> >> CSPRNG_METHOD = openssl >> >> In the config for NonStop. Should that not have worked? > >In your original report, you said > >>> I thought we did not have a direct reference to OpenSSL. What do I >>> need here to resolve this? > >I misread it as "I did not directly ask to use OpenSSL---why am I seeing breakage >from RAND_bytes() that is an OpenSSL thing?", and where my suggestion to look >for CSPRNG_METHOD came from. > >Downthread, folks seem to have figured out that OpenSSL support failed to >include a necessary header and link with libraries, while I was offline yesterday, so >hopefully all is well? > >Since d073bdc6 (Merge branch 'bc/csprng-mktemps', 2022-02-11) the CSPRNG >code has been in 'master/main' and the topic was merged to 'next' much earlier, >at 2e32375c (Merge branch 'bc/csprng-mktemps' >into next, 2022-02-04). I was puzzled why it took this long for your report to come, >as I somehow thought you've been quite good at reporting portability issues to >your platform quickly, and was wondering if we broke something between the >time we merged it to 'next' and -rc0, but it seems that it was not working from the >beginning X-<. The 2.35.1 build happened on 29 Jan 2022, which appears to be before the change. That's why I didn't report it. This was the first build/test since then. So, no surprise actually. The build was done on commit 4c53a8c20f8984adb226293a3ffd7b88c3f4ac1a. At least we know why the problem only showed up now. As I said, it's 50 hours to run the test cycle on ia64, so I only run this when an announcement happens. Regards, Randall