bug#15150: Possible bug of ln or gfortran of cygwin

[Namito]

(2013/08/21 23:11), Pádraig Brady wrote:
> tag 15150 notabug
> close 15150
> stop
>
> On 08/21/2013 07:56 AM, Namito wrote:
> > I tried to compile following using gfortran 4.8.1-1
> >
> > include 'bb/test2.f'
> > a(1)=1.0
> > a(2)=2.0
> > b=a(1)+a(2)
> > write(6,*) b
> > stop
> > end
> >
> > When bb/test2.f is a real file, no compile error is generated.
> > When aa/test2.f is a real file and bb/test2.f is a symbolic link of
> > /aa/test2.f,
> > Error 'Can't open included file '/bb/test2.f'
> > is displayed.
> > ln -s aa bb
> > was a command to creat symbolic link.
> I doubt a bug in ln.
> Notice that above an absolute path of '/bb/test2.f' is reported.
> I'd guess that absolute path was incorrectly specified to `ln -s` when creating 
> the link,
> or more unlikely that gfortran is handling relative symlinks incorrectly.
>
> You can exclude gfortran by doing something like:
> (cd bb && { test -e test2.f && echo 'link ok'; })
>
> Generally one should send the ln --version when reporting bugs.
>
> thanks,
> Pádraig.

Let me make one correction af first.

When aa/test2.f is a real file and bb/test2.f is a symbolic link of
aa/test2.f,
Error 'Can't open included file '/bb/test2.f'
is displayed.

link ok
was displayed when I did,
(cd bb && { test -e test2.f && echo 'link ok'; })

Also, version of ln is 8.15