X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org From: Sam Steingold To: cygwin AT cygwin DOT com, Charles Wilson Subject: Re: i686-w64-mingw32-gcc & ntifs.h In-Reply-To: <4E52D5C5.4060106@cwilson.fastmail.fm> (Charles Wilson's message of "Mon, 22 Aug 2011 18:18:45 -0400") References: <4E4D9487 DOT 4080103 AT users DOT sourceforge DOT net> <4E4E38B9 DOT 9010803 AT users DOT sourceforge DOT net> <20110819120044 DOT GA2506 AT calimero DOT vinschen DOT de> <4E4F08D3 DOT 3060007 AT users DOT sourceforge DOT net> <87fwkunsna DOT fsf AT gnu DOT org> <4E5229ED DOT 9050805 AT users DOT sourceforge DOT net> <4E52D5C5 DOT 4060106 AT cwilson DOT fastmail DOT fm> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) Mail-Copies-To: never Reply-To: sds AT gnu DOT org X-Disclaimer: You should not expect anyone to agree with me. Mail-Followup-To: cygwin AT cygwin DOT com, Charles Wilson Date: Tue, 23 Aug 2011 10:23:43 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > * Charles Wilson [2011-08-22 18:18:45 -0400]: > > On 8/22/2011 5:13 PM, Sam Steingold wrote: >> PS. Why are cygwin/mingw and msys/mingw so different? > > They are not different. In fact, 'cygwin/mingw.org' and 'msys/mingw.org' > are identical (except for the emulation environment under which they > run: msys vs. cygwin). > > You're confused by the existence of the separate "mingw64" project. > > There are three different "flavors" of mingw-ish compilers: > 1. mingw.org (32bit only) > > 2. mingw64.sf.net > a) 32bit > b) 64bit > > Cygwin provides cross-compiler toolchains for each of these three "flavors": > > 1) i686-pc-mingw32-gcc > 2a) i686-w64-mingw32-gcc > 2b) x86_64-w64-mingw32-gcc OK, thanks. The bottom line is that I should stick with i686-pc-mingw32-gcc and forget the others even exist. Cool. Now, $ egrep -r '#define *STATUS_SUCCESS' /usr/*-mingw32/sys-root/mingw/include/ /usr/i686-pc-mingw32/sys-root/mingw/include/ddk/ntstatus.h:#define STATUS_SUCCESS ((NTSTATUS)0x00000000L) /usr/i686-pc-mingw32/sys-root/mingw/include/ntdef.h:#define STATUS_SUCCESS ((NTSTATUS)0) /usr/i686-pc-mingw32/sys-root/mingw/include/subauth.h:#define STATUS_SUCCESS 0 /usr/i686-w64-mingw32/sys-root/mingw/include/ntstatus.h:#define STATUS_SUCCESS ((NTSTATUS)0x00000000L) /usr/i686-w64-mingw32/sys-root/mingw/include/subauth.h:#define STATUS_SUCCESS ((NTSTATUS)0x00000000L) /usr/x86_64-w64-mingw32/sys-root/mingw/include/ntstatus.h:#define STATUS_SUCCESS ((NTSTATUS)0x00000000L) /usr/x86_64-w64-mingw32/sys-root/mingw/include/subauth.h:#define STATUS_SUCCESS ((NTSTATUS)0x00000000L) Which one should I include for STATUS_SUCCESS: ddk/ntstatus or ntdef? (I am using i686-pc-mingw32-gcc now exclusively). Note that both w64 versions have ntstatus.h in the right place (defined as the place where visual studio places it). Is this a known bug in mingw? Will it be fixed? -- Sam Steingold (http://sds.podval.org/) on CentOS release 5.6 (Final) X 11.0.60900031 http://openvotingconsortium.org http://jihadwatch.org http://palestinefacts.org http://www.memritv.org http://mideasttruth.com http://ffii.org Lottery is a tax on statistics ignorants. MS is a tax on computer-idiots. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple