This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: [OT] Re: question about cygwin package
On Sat, Feb 27, 2010 at 10:48:50PM +0100, Vincent Richomme wrote:
>On Sat, 27 Feb 2010 21:36:15 +0000, Dave Korn
><dave.korn.cygwin@googlemail.com> 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