X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4E4CE854.2020706@users.sourceforge.net> References: <4E4CE854 DOT 2020706 AT users DOT sourceforge DOT net> From: =?ISO-8859-1?Q?Fr=E9d=E9ric_Bron?= Date: Thu, 18 Aug 2011 15:56:43 +0200 Message-ID: Subject: Re: i686-XXX-mingw32 compilers and __MINGW32_MINOR_VERSION macro: 3.18 or 3.11? To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p7IDvf6A004582 > Just bump it up and see if there are any issues, the mingw-w64 toolchain > uses its own header set and the numbers don't always reflect mingw.org > releases, since the macros in there are mainly for compatibility. > > You want to check instead for __MINGW64_VERSION_MAJOR on mingw-w64. neither __MINGW64__, nor __MINGW64_VERSION_MAJOR are defined because I am targetting win32, not win64, even if I use w64 compiler. So this does not help. Any other clue? Frédéric -- 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