From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id E6B87386F826 for ; Mon, 28 Sep 2020 15:29:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E6B87386F826 Received: from fencepost.gnu.org ([2001:470:142:3::e]:45691) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kMv5g-0006Ay-G9; Mon, 28 Sep 2020 11:29:24 -0400 Received: from [176.228.60.248] (port=1990 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kMv5W-0003Lm-0x; Mon, 28 Sep 2020 11:29:16 -0400 Date: Mon, 28 Sep 2020 18:29:01 +0300 Message-Id: <83r1qlly2q.fsf@gnu.org> From: Eli Zaretskii To: cbiesinger@google.com CC: gdb@sourceware.org In-Reply-To: <83sgb2kjr8.fsf@gnu.org> (message from Eli Zaretskii via Gdb on Mon, 28 Sep 2020 18:23:39 +0300) Subject: Re: Unable to build GDB on Windows References: <833632m10q.fsf@gnu.org> <83zh5aklls.fsf@gnu.org> <83sgb2kjr8.fsf@gnu.org> X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Sep 2020 15:29:26 -0000 > Date: Mon, 28 Sep 2020 18:23:39 +0300 > From: Eli Zaretskii via Gdb > Cc: gdb@sourceware.org > > > From: Christian Biesinger > > Date: Mon, 28 Sep 2020 17:17:49 +0200 > > Cc: simon.cook@embecosm.com, Reuben Thomas via Gdb > > > > Hmm that sounds odd, usually the way the Windows SDK works is that > > this only depends on what you #define, not what you build on > > (especially _WIN32_WINNT) > > Well, that's true, but how many will use "CPPFLAGS=-D_WIN32_WINNT=..." > when configuring GDB? The default is buried somewhere in the MinGW > headers, and guess what it is? And actually, in this case the above is not relevant. Because getrandom.c bases its logic on the configure-time test that results in HAVE_LIB_BCRYPT defined to either 1 or zero. It doesn't look at _WIN32_WINNT at all. So yes, the result depends on whether you build GDB on a system with or without bcrypt.dll.