This is the mail archive of the
mailing list for the Cygwin project.
Re: gcc 3.2 and symbolic links problem
- From: Larry Hall <cygwin-lh at cygwin dot com>
- To: Gerry Reno <grenoml at yahoo dot com>, cygwin at cygwin dot com
- Date: Sat, 06 Sep 2003 19:34:12 -0400
- Subject: Re: gcc 3.2 and symbolic links problem
- References: <email@example.com>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
This is Mingw's gcc. You need to make sure you invoke Cygwin's gcc.
It will understand the symlink.
At 07:18 PM 9/6/2003, Gerry Reno you wrote:
>The error looks like:
>$ ls -l myfile.c
>lrwxrwxrwx 1 greno None 110 Sep 6 19:06 myfile.c ->
>gcc -c myfile.c -o myfile.o
>gcc.exe: myfile.c: No such file or directory
>gcc.exe: no input files
>gcc.exe (GCC) 3.2.3 (mingw special 20030504-1)
>--- Gerry Reno <firstname.lastname@example.org> wrote:
>> I recently upgraded to cygwin 1.5.3 and to Mingw 3.0.0 and I now
>> notice that gcc will fail when trying to compile files that are
>> symlinks. I tried deleting and recreating the link - still fails. I
>> can read all the files and use all other tools with these symlinks.
>> Has anyone else seen this problem with gcc 3.2?
>> Gerry Reno
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html