2013/6/19 Corinna Vinschen <[email protected]>
> On Jun 19 12:34, Corinna Vinschen wrote:
> > On Jun 19 14:28, LRN wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > On 19.06.2013 13:55, Corinna Vinschen wrote:
> > > > On Jun 19 13:32, LRN wrote:
> > > >> On 19.06.2013 12:57, Corinna Vinschen wrote:
> > > >>> On Jun 19 12:08, LRN wrote:
> > > >>>> To be fair here, i've tried the MSYS=winsymlinks:nativestrict,
> and first
> > > >>>> thing i hit was AC_PROG_LN_S. That macro explicitly refuses to
> use `ln
> > > >>>> - -s' provided by MSYS or Cygwin, asking for 100% POSIX
> compliance.
> > > >>>
> > > >>> On Cygwin? Not that I'm aware of. I tested the AC_PROG_LN_S macro
> > > >>> on Cygwin and the LN_S setting is 'ls -s' afterwards. That's with
> > > >>> autoconf-2.69.
> > > >>
> > > >> My mistake, i meant _AS_LN_S_PREPARE, not AC_PROG_LN_S.
> > > >
> > > > _AS_LN_S_PREPARE also yields `ln -s' on Cygwin. Just tested.
> > > It shouldn't. Probably. I think.
> > >
> > > It (is/should be) impossible to create an NTFS symlink to non-existing
> > > target in Cygwin or MSys (since the target must exist to be able to
> > > create an link of the right type).
> > >
> > > Are you sure that your _AS_LN_S_PREPARE does this:
> >
> > yes.
> >
> > > [...]
> > > and that you're using winsymlinks:nativestrict?
> >
> > No. I'm using any one of the other variations of symlinks. nativestrict
> > was a compromise with my fellow co-maintainer. The default symlinks
> > and winsymlinks:lnk always work, winsymlinks:native falls back to the
> > default symlinks if creating the native symlink doesn't work.
> >
> > winsymlinks:nativestrict is a special case, not the norm.
>
> As a sidenote:
>
> What's really sad is the fact that a native symlink contains the
> information if the target is a file or directory, and worse, that
> non-Cygwin tools fail if the file/directory information in the symlink
> is wrong. That alone disallows to create native symlinks to non-existing
> targets, since you never know whether the target will be file or dir.
> I'm totally baffled how a simple functionality like creating symlinks
> can be so screwed up, with no hope in sight.
>
I'm sorry, but all documentation I can find about NTFS reparse points and
softlinks etc. say explicitely that you can create a softlink to a
nonexistent file:
http://msdn.microsoft.com/en-us/library/aa365460%28VS.85%29.aspx
So either something is XP specific and not clearly showing on MSDN, or I'm
misunderstanding the problem.
Ruben
>
>
> Corinna
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Mingw-w64-public mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
