From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7131 invoked by alias); 30 Apr 2019 17:50:35 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 7114 invoked by uid 89); 30 Apr 2019 17:50:35 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SBL_CSS,SPF_PASS autolearn=no version=3.3.1 spammy=H*RU:sk:broadba, HX-Spam-Relays-External:sk:broadba, H*UA:x64, H*UA:Win64 X-HELO: mail-lj1-f172.google.com Received: from mail-lj1-f172.google.com (HELO mail-lj1-f172.google.com) (209.85.208.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 30 Apr 2019 17:50:33 +0000 Received: by mail-lj1-f172.google.com with SMTP id t1so3511459lje.10 for ; Tue, 30 Apr 2019 10:50:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:autocrypt:message-id:date:user-agent :mime-version:in-reply-to; bh=AKQFCFHw0P9RDuQEaCM1m5hg1Tza3MOW6FbwZmJxuMU=; b=bU1gPI9CxIfxyQFrj1eHSZmDntbrAyq1bkfmSfkMRC0GEv9YEr3o8jhCNn19/2Sztv 3B4KsVK5UTA9DUknHxKW+OITRu/IMJslmdjRT/2xN7tTWjv1ul6hzhIejoiuCCZZ06ZU 3+EWD50BcgmaWLMFE1HF4PJ7ub+m4FA5Gf5ciNR9PHuQkTUEYK/pbvsQBA8qdPacEhWn vxp0/l3bKYZcYSy7JlQp+u+R6TmXRWiB14c60AcXlxFaHKsr8LTVxFsvMnevQW8TbEwC 5tGhzoEz4LVroUq0ghFpTCBBIB+UioeoowpsjrbA2umkWsOmQKAS1tbkY0ot1sQaw3K1 IW9w== Return-Path: Received: from [192.168.4.39] (broadband-95-84-200-6.ip.moscow.rt.ru. [95.84.200.6]) by smtp.gmail.com with ESMTPSA id f18sm8049538lfh.39.2019.04.30.10.50.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Apr 2019 10:50:30 -0700 (PDT) Subject: Re: Fix compilation using mingw.org's MinGW To: gdb-patches@sourceware.org References: <835zrbe36c.fsf@gnu.org> <250801eb-14f6-5a35-0556-cf5797dd8a7b@redhat.com> <83y347cfbu.fsf@gnu.org> <556cefd7-47ce-54ab-a228-2c727aab4179@redhat.com> <83d0lick7o.fsf@gnu.org> <93ccb0fa-8a05-60ff-d1a8-85d5663b8d16@redhat.com> <831s1murm2.fsf@gnu.org> <365578d2-82fb-8860-26e6-1b31a63632ed@gmail.com> <83imuvsefv.fsf@gnu.org> From: LRN Message-ID: <3e691b80-2d3c-8e7d-60c0-5f5df4ea2f36@gmail.com> Date: Tue, 30 Apr 2019 17:50:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <83imuvsefv.fsf@gnu.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="wifspgJ7KtsJ6ZfHaAVOsg4ZuuZEVlhhs" X-IsSubscribed: yes X-SW-Source: 2019-04/txt/msg00663.txt.bz2 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --wifspgJ7KtsJ6ZfHaAVOsg4ZuuZEVlhhs Content-Type: multipart/mixed; boundary="0qJuozGTBuVveka0JGbktkiXNQgqLBi3i"; protected-headers="v1" From: LRN To: gdb-patches@sourceware.org Message-ID: <3e691b80-2d3c-8e7d-60c0-5f5df4ea2f36@gmail.com> Subject: Re: Fix compilation using mingw.org's MinGW --0qJuozGTBuVveka0JGbktkiXNQgqLBi3i Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Content-length: 751 On 30.04.2019 18:25, Eli Zaretskii wrote: >> From: LRN >> Date: Tue, 30 Apr 2019 16:05:55 +0300 >> >>> - IIRC, Cygwin uses the same w32api headers as mingw.org. I don't know >>> whether Cygwin sets _WIN32_WINNT to a higher number already; we >>> haven't heard any complaints, so I guess it does. >>> >> >> Cygwin uses mingw-w64. >=20 > Maybe I'm missing something, but I don't think this is relevant. > _WIN32_WINNT is not a MinGW invention, it's an official symbol in > Windows headers, so all Windows compilers need to support it in the > same way and with the same semantics. The only difference is the > default value. >=20 > Am I missing something? >=20 I replied to the "Cygwin uses the same w32api headers as mingw.org" part on= ly. --0qJuozGTBuVveka0JGbktkiXNQgqLBi3i-- --wifspgJ7KtsJ6ZfHaAVOsg4ZuuZEVlhhs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" Content-length: 833 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE4MWzR43wYaAzEA49ja3pJ2dZunQFAlzIit4ACgkQja3pJ2dZ unSONw//f/tBUfni1JFmHArogwipLzMee7V632coGqy3ijzk8eJX5HtBy/WrZ0tG 3q9kGKCWbrGgKh1L7ivAf5DcqJV9qGex4pox2ODwLMR/qUJbz6cviflUrV2fDIKd gVGNxVKQqz7eRqkfOY0qK4YD0sBdcFCR4hZw/qcQmSEL3QaxVcOB44JH5CbG9seX Fchg5gss/x/wAMi4I7+3AaRwkYNSNBh48w6CeBZ81BYXIV1RmJEdXntS9HjjKown Xh4p0Fe/nxEgdtpo/kDfaZOe2WFCgejW1Y1PH3ThEwbCeDLfYmUHrtHWWeXo5+Bz l8lXYpRW+siWf3JbKglpbIvysVxXz7lz1ch744dlFiErOllT4qlseLt5ge7U7LHl h4TZCgcvd2JlhI5MC0Xu2SPghaCAPV2PdyP36TwRLBDt+drybZHSg1ea3BuWlZyp 2vdI/JLVrG1hcAmqgTr8xImMIcKM7q6UPl54a3Vq4SGxgj4wl4Zje1zWGW4HID8Q JQP3DDm76JP2HvfY9idsGt3t6tYjmgG2R0BnxsC5ph5m3HSyPnKOdNF266KntzPg H9fORwgrNpPN99bPxLlZECALTzm8rOBU2zDbE1mSmZjoo4Goc2Zy77KzdTtsg+H1 F8CALRAjz56BUnh6109kR/yO3thAXlcaIRTIiYaOxqz9g5OcuFg= =6P4F -----END PGP SIGNATURE----- --wifspgJ7KtsJ6ZfHaAVOsg4ZuuZEVlhhs--