This is the mail archive of the
mailing list for the Cygwin project.
Re: gcc 3.2 and symbolic links problem
- From: Gerry Reno <grenoml at yahoo dot com>
- To: Max Bowsher <maxb at ukf dot net>, cygwin at cygwin dot com
- Date: Sat, 6 Sep 2003 16:43:14 -0700 (PDT)
- Subject: Re: gcc 3.2 and symbolic links problem
I have compiled these programs before with the symlinks. Yes it was
with cygwin and not mingw. I just changed my PATH and its compiling.
--- Max Bowsher <firstname.lastname@example.org> wrote:
> 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
> to understand Cygwin symlinks.
> > --- Gerry Reno <email@example.com> 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.
> >> can read all the files and use all other tools with these
> >> Has anyone else seen this problem with gcc 3.2?
> No, because you are *not* using gcc 3.2.
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html