Gerry Reno wrote: > The error looks like: > > $ ls -l myfile.c > lrwxrwxrwx 1 greno None 110 Sep 6 19:06 myfile.c -> > ../myfile.c > > gcc -c myfile.c -o myfile.o > gcc.exe: myfile.c: No such file or directory > gcc.exe: no input files > > $gcc --version > gcc.exe (GCC) 3.2.3 (mingw special 20030504-1)
*MINGW*. It shouldn't surprise you that a native Windows program is unable to understand Cygwin symlinks. > --- Gerry Reno <[EMAIL PROTECTED]> 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? No, because you are *not* using gcc 3.2. Max. -- 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/
