This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc: installation problem, cannot exec 'cc1'


Thomas Antony wrote:

> $ ls -l /usr/lib/gcc/i686-pc-mingw32/3.4.4/
> total 1234
> -rwxr-xr--+ 1 Tom Users     547 Jan  6 20:44 cc1.exe.lnk
> -rwxr-xr--+ 1 Tom Users     567 Jan  6 20:44 cc1plus.exe.lnk
> -rwxr-xr--+ 1 Tom Users     573 Jan  6 20:44 collect2.exe.lnk
> -rwx------+ 1 Tom None      412 May 24  2005 crtbegin.o
> -rwx------+ 1 Tom None      492 May 24  2005 crtend.o
> drwxrwxr--+ 2 Tom Users       0 Jan 12 08:18 debug
> drwxrwxr--+ 3 Tom Users       0 Jan 12 08:18 include
> drwxrwxr--+ 3 Tom Users       0 Jan 12 08:18 install-tools
> -rwx------+ 1 Tom None    52594 May 24  2005 libgcc.a
> -rwx------+ 1 Tom None     9772 May 24  2005 libgcov.a
> -rwx------+ 1 Tom None  1063604 May 24  2005 libstdc++.a
> -rwx------+ 1 Tom None      685 May 24  2005 libstdc++.la
> -rwx------+ 1 Tom None   116074 May 24  2005 libsupc++.a
> -rwx------+ 1 Tom None      685 May 24  2005 libsupc++.la
> -rwxr-xr--+ 1 Tom Users     537 Jan  6 20:44 specs.lnk

That still looks fishy.  Those should be symlinks, and ls should show
them as such, not as .lnk files.  Out of curiosity, from a CMD prompt in
that dir what does "attrib cc1.exe.lnk" say?  Does it have the R bit
set?  I checked your cygcheck and it appears that you have Cygwin
installed on C: which is NTFS, so FAT shouldn't be an issue.  You don't
happen to have anything set in the CYGWIN environment variable that
would affect symlinks?  What happens if you manually run the preremove
and postinstall scripts from a bash prompt, i.e. ".
/etc/preremove/gcc-mingw-core.sh; .
/etc/postinstall/gcc-mingw-core.sh.done".  That should remove and then
recreate those files.  Do you have working symlinks then?

> I ran the cc1.exe link from windows. It gave me error that cygwin1.dll
> couldnt be found. But on adding the Cygwin/bin directory to the PATH
> (in windows), removed that error and CC1.exe shows a blank console
> window. But the error while compiling still persists.

That's not really a useful debugging method.  Running any Cygwin binary
without /bin in the path is going to give an error about a missing DLL. 
And cc1 is not meant to be invoked directly so it won't print anything
useful.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]