From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29713 invoked by alias); 28 Feb 2010 00:39:10 -0000 Received: (qmail 29695 invoked by uid 22791); 28 Feb 2010 00:39:09 -0000 X-Spam-Check-By: sourceware.org Received: from pool-173-48-46-17.bstnma.fios.verizon.net (HELO cgf.cx) (173.48.46.17) by sourceware.org (qpsmtpd/0.83/v0.83-20-g38e4449) with ESMTP; Sun, 28 Feb 2010 00:39:05 +0000 Received: from ednor.cgf.cx (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 68BA813C0D0 for ; Sat, 27 Feb 2010 19:39:03 -0500 (EST) Received: by ednor.cgf.cx (Postfix, from userid 201) id 3588A2B352; Sat, 27 Feb 2010 19:39:03 -0500 (EST) Date: Sun, 28 Feb 2010 00:39:00 -0000 From: Christopher Faylor To: cygwin-talk@cygwin.com Subject: Re: [OT] Re: question about cygwin package Message-ID: <20100228003902.GA30204@ednor.casa.cgf.cx> Reply-To: cygwin-talk@cygwin.com Mail-Followup-To: cygwin-talk@cygwin.com References: <203f8122bd16fb669eab1f46bb89a0e8@mail.smartmobili.com> <4B89904F.60305@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Vulgar and Unprofessional Cygwin-Talk List Mail-Followup-To: cygwin-talk@cygwin.com X-SW-Source: 2010-q1/txt/msg00051.txt.bz2 On Sat, Feb 27, 2010 at 10:48:50PM +0100, Vincent Richomme wrote: >On Sat, 27 Feb 2010 21:36:15 +0000, Dave Korn > wrote: >> On 27/02/2010 20:48, Vincent Richomme wrote: >>>> Add '-v' to see how gcc is using relative paths to look for cc1.exe >(and >>>> presumably failing). >> >>> $ gcc -v test.c >> >>> cc1 -quiet -v -iprefix >> >> Hmm, that means it has no idea at all where to find cc1. So take a >look >> at >> what "gcc -print-search-dirs" says for "programs:". >> > >programs: >=c:/developer/easymingw-devel/mingw32/bin/../libexec/gcc/i686-w64-min >w32/4.4.4/;c:/developer/easymingw-devel/mingw32/bin/../libexec/gcc/;/usr/libexe >/gcc/i686-w64-mingw32/4.4.4/;/usr/libexec/gcc/i686-w64-mingw32/;/usr/lib/gcc/i6 >6-w64-mingw32/4.4.4/;/usr/lib/gcc/i686-w64-mingw32/;c:/developer/easymingw-deve >/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.4.4/../../../../i686-w64-mingw32/bin >i686-w64-mingw32/4.4.4/;c:/developer/easymingw-devel/mingw32/bin/../lib/gcc/i68 >-w64-mingw32/4.4.4/../../../../i686-w64-mingw32/bin/ > >Ok so now I understand why it doesn't work it searches inside >.../mingw32/bin/../libexec >but programs are in ../mingw32/bin/../usr/libexec >So I suppose my only choice is to keep using mingw logic. I don't think this discussion is even appropriate for the cygwin-talk list. While msys may be somewhat related to cygwin, I have to draw the line at discussions about msys and mingw here. If you're having msys or mingw issues there are much better mailing lists to use than ones with the word "cygwin" in them. cgf