On Jun 19 12:08, LRN wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 12.06.2013 18:51, Alexpux wrote: > > среда, 12 июня 2013 г. в 18:00, Corinna Vinschen написал: > >> On Jun 12 15:50, Alexpux wrote: > >>> среда, 12 июня 2013 г. в 14:47, Corinna Vinschen написал: > >>>> On Jun 11 21:10, Алексей Павлов wrote: > >>>>> 4. Replaced Cygwin symlinks with copying (we can investigate an option > >>>>> for > >>>>> mklink symlinks on Vista and above but this is a topic for discussion - > >>>>> MSYS compliant software tend to work around most ln-as-cp issues when > >>>>> possible anyway). > >>>>> > >>>> > >>>> I said my share about what I think of copying files when the application > >>>> expects to get a symlink. It's wrong. It's dangerous. You still have > >>>> the CYGWIN=winsymlinks:lnk and CYGWIN=winsymlinks:native or > >>>> CYGWIN=winsymlinks:nativestrict options available when using Cygwin > >>>> unchanged (http://cygwin.com/cygwin-ug-net/using-cygwinenv.html) > >>>> > >>> > >>> > >>> Yes it dangerous but native symlinks work need elevated shell and OS > >>> Vista+ > >> > >> Again, if you need a copy, use cp, not ln -s. It's plainly a bug in the > >> scripts or tools you're using, if they use ln -s (or symlink(2)) when > >> called in a Mingw environment. Neither of them must rely on symlinks. > >> > >> > > > > And I need patch every configure script and Makefile to fix it? > 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. > So it might turn out that `ln -s' hack would only affect corner-cases > (where people just write `ln -s' in makefiles and such). > > Later today, when i get a new MSYS2 build (based upon the latest Cygwin > with fixed symlinks in case of a different cygdrive prefix), i'll hack > AC_PROG_LN_S to allow MSYS2's `ln -s' to be used, and will check if that > works (i expect that it would). > > I could also replace /usr/bin/ln with a wrapper script that would log > all invocations of `ln' with `-s' to count exactly how much it is being > used (that said, it won't cover things like `lndir' which is use when > needed). What about leaving the symlink(2) function alone and rather just replace the ln(1) tool with a wrapper which calls cp(1) in case of the -s option instead, some ln.orig.exe otherwise? 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
