https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88041

Johannes Pfau <johannespfau at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |johannespfau at gmail dot com

--- Comment #5 from Johannes Pfau <johannespfau at gmail dot com> ---
For reference, this makes running the testsuite on windows/msys2 hosts somewhat
more complicated:

On these systems, ln -s is implemented by copying SRC to DST instead of
creating proper links [1]. (I'm not sure whether the TCL file link command
actually calls ln on MSYS2, but it seems to do so, as the observed effect is
just this: a copy of the directory).

It is possible to configure MSYS2 to use proper NTFS symlinks instead [2], but
then running the testuite will always require administrator privileges on older
windows versions. On newer windows versions, mklink can now be used as normal
user iff the windows developer mode is enabled [3]. However, the ln shipped
with MSYS2 does not yet make use of this feature[4].

Not sure if this really is a problem or if there's a better solution. For now,
configuring ln to use windows symlinks and building gcc as admin should work.
An alternative is to just manually create that one symlink. The best solution
is probably to just use a cross-compiler for testing and build on linux ;-)

[1] https://sourceforge.net/p/msys2/tickets/41/
[2] https://www.joshkel.com/2018/01/18/symlinks-in-windows/
[3]
https://www.wintellect.com/non-admin-users-can-now-create-symlinks-windows-10/
[4] https://github.com/Alexpux/MSYS2-packages/issues/1219

Reply via email to