gcc packaging bug [was: Re: can not exec cc1.exe]

Jim Marshall wrote: > all of the mingw directories were still there. I manually deleted all > the files in these directories (/usr/i686-pc-mingw and > /usr/lib/gcc/i686-pc-mingw32). I then reran the cygwin setup and had it > install the mingw tools. This fixed the problem. I am presuming that th

Re: can not exec cc1.exe

Brian Dessent wrote: Jim Marshall wrote: Here is the cygcheck -svr output. Hmm, you're using a local NTFS drive and $CYGWIN is not set to anything strage. So no more clues there. What are the attributes of the .lnk files? What happens if you manually delete them and recreate them as workin

Re: can not exec cc1.exe

Jim Marshall wrote: > Here is the cygcheck -svr output. Hmm, you're using a local NTFS drive and $CYGWIN is not set to anything strage. So no more clues there. What are the attributes of the .lnk files? What happens if you manually delete them and recreate them as working symlinks by hand? Br

Re: can not exec cc1.exe

Brian Dessent wrote: Jim Marshall wrote: I have tried uninstalling and reinstalling the mingw packages with no luck. The links "appear" ok in the mingw directory: /usr/i686-pc-mingw32 $ ls bin.lnk* include.lnk* lib.lnk* You've got something installed incorrectly then. If they are showin

Re: can not exec cc1.exe

Jim Marshall wrote: > I have tried uninstalling and reinstalling the mingw packages with no > luck. The links "appear" ok in the mingw directory: > > /usr/i686-pc-mingw32 > $ ls > bin.lnk* include.lnk* lib.lnk* You've got something installed incorrectly then. If they are showing as .lnk fil