From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26270 invoked by alias); 29 Aug 2012 16:08:39 -0000 Received: (qmail 26256 invoked by uid 22791); 29 Aug 2012 16:08:35 -0000 X-SWARE-Spam-Status: No, hits=-0.1 required=5.0 tests=AWL,BAYES_05,KHOP_THREADED,URI_HEX X-Spam-Check-By: sourceware.org Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 29 Aug 2012 16:08:20 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1T6koV-0007fp-Rw for cygwin@cygwin.com; Wed, 29 Aug 2012 09:08:19 -0700 Date: Wed, 29 Aug 2012 18:02:00 -0000 From: thoni56 To: cygwin@cygwin.com Message-ID: <1346256499860-92389.post@n5.nabble.com> In-Reply-To: <503DC812.5060704@users.sourceforge.net> References: <1346220462071-92376.post@n5.nabble.com> <1346220956451-92378.post@n5.nabble.com> <503DC812.5060704@users.sourceforge.net> Subject: Re: mingw32-gcc and posix paths MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-08/txt/msg00635.txt.bz2 JonY-6 wrote > > On 8/29/2012 14:15, thoni56 wrote: >> >> thoni56 wrote >>> >>> I'm in the process of going from gcc3 to gcc4. For one project I need to >>> build both cygwin and win32 executables so "-mno-cygwin" to >>> "mingw32-gcc" >>> was an initial hurdle. >>> >>> However that is now sorted out, but one thing puzzles me. If the mingw32 >>> is a cygwin cross-compiler why does it not accept paths in the host >>> format >>> (meaning cygwin, posix)? To me this seems very natural. Maybe I'm >>> biased, >>> but I see no other tools do that, expecting the command line to have the >>> format of the *target*. >>> >>> mingw32-gcc also produces .d files in its native format by the way. >>> >> >> I forgot to add that it is really this .d thing that makes it >> problematic. >> The makefiles generate separate subdirectories for various targets and >> also >> sets CFLAGS, CC, LINK et al. differently to allow different settings (and >> compilers, was my theory) for the different targets. >> >> Since mingw32-gcc and gcc generates .d files in incompatible formats (gcc >> really doesn't like "c:\..." in its .d files...) and those are included >> in >> the make file, even using different make:s does not solve the problem for >> me. >> >> Any ideas? > > Cygwin does not and never has provided a "mingw32-gcc", but it has a > "i686-pc-mingw32-gcc", it is likely you used those from mingw.org. > > mingw.org provides native toolchains, so it is not Cygwin aware, it > would explain your path issues. > Ooops. I was misled by a comment to http://stackoverflow.com/questions/3776098/cygwin-how-to-actually-use-gcc-mingw this question on Stackoverflow . As it happened I had a very old version of mingw32-gcc installed and in my PATH. Sorry about that! "i686-w64-mingw32-gcc" (which it is in my cygwin) works perfectly. Thanks! -- View this message in context: http://cygwin.1069669.n5.nabble.com/mingw32-gcc-and-posix-paths-tp92376p92389.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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