Re: [PATCH v3 2/2] x86_64/i386 fenv: Replace symlink with include fenv_stub.c

Corinna Vinschen <[email protected]>
Newsgroups gmane.comp.lib.newlib
Message-ID <[email protected]>
Hey Joel,

the patch itself is fine, but I'm puzzeling over the commit message.

On Feb 19 08:03, Joel Sherrill wrote:
> Having symlinks for these files led to an issue reported to the
> RTEMS Project that showed up on MSYS2. Per the report we received,

MSYS2 is a Cygwin clone which understands any kind of Cygwin symlink,
an invention from way back when Windows really didn't have symlinks.

> there are no such things as links on Windows,

NTFS has symlinks since Windows Vista, about 2007.

> it is a copy of the
> file and if it does not exist it has to fail. The working all depends
> on the order the tar file is built. If the links appear in the tar file
> before the source exists, it cannot copy the file.

Isn't that just somebody using an inadequate tool here?  Do you have a
pointer to a bugzilla/github/whatever issue clarifying the actual
problem?


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAl5OSrQACgkQ9TYGna5E
T6A27w//QXNdq7vkZzNjY9xQz2RgT9Wbes9dmj87T/VKS2lu2V9Vve+efgvDjgqg
dxdqzpeIiub1vQ1CeIWCMAJAG8mKSGH0YV4LT4d9ptKzEQhjrzJaVTLVReKR4UnG
kjizFu9ZQ+fALlns33PZj4mAc/4ZcEWLy2EzSUyNhoFPzlsZBoSbHzlv1E7rE6g7
InlYooSZarknlYRBZgC/heHUTD4hSRa+Uw0YETNqym6Fzslyte51QYpr4DeINFSP
vniryHhutNPsnxh56+88eLN+TPmfHCCS2ECELABokEZmssdCdcSxVz+MRst7vWAy
hURPBo90Q9FlDoHiU8osjmnXpEJueqDunRtv5zsLsvWnakqKIfERCzToBrMjv5Pe
dYMO9Ux59f/vmsMB2XnNiV+3TkDOrC4HbIZCaHBNy1O4FxcF0rbuHtV0bsehgyEK
dok0OE1LAlnMmUpYXjk+c1a2pDKHhkF5D9dvB2lHBan/gkIS6+R6KhxiFe5xlD5k
oe4MZe8yT/hfSYsKQR8rTOJEoaG8G2YPaVDUpwzpkG/CsQHjuuKCh0iuK/O+iLRh
1U8FzFlRNKtj1Z4DtqbeQntmZ7gaDHMVqQCinqz5MKznD6gk3SUTprhmV89X+vIA
VI4l/rZYvCczhAoxEtln94VE2YGfBZjf6RhFJQZ+pF8/b1mGBjo=
=wa0e
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.