From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Setup shows errors from gnuplot-base.dash and python38-devel.sh
Date: Thu, 15 Jul 2021 18:18:21 +0200 [thread overview]
Message-ID: <87fswfzh2q.fsf@Otto.invalid> (raw)
In-Reply-To: <CAJ1FpuPt2Aa9JzYmoO2TmB31JnonGi9xtSkxrh7pgUjvvrWndw@mail.gmail.com> (Doug Henderson via Cygwin's message of "Thu, 15 Jul 2021 10:04:13 -0600")
Doug Henderson via Cygwin writes:
> Alternatives does not work correctly when CYGWIN=nativestrict. Perhaps
> it is trying to create a link before the link target exists. Unlike
> Linux, Windows does not allow creating symbolic links to non-existent
> targets.
Which is one reason why Windows symlinks are not POSIX symlinks. The
real reason is that you need to need to tell Windows whether you're
pointing the symlink at a directory or a file when the target does not
yet exist.
> Am I the only person that uses "CYGWIN=winsymlinks:nativestrict" ???
Well, you should certainly pay more attention to where, when and how it
breaks. It papers over one of the differences between the POSIX and
Windows world, but creates another gap elsewhere.
This is exactly why I have backed out the commit that uses the CYGWIN
environment variable in setup.exe.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
next prev parent reply other threads:[~2021-07-15 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 16:59 Doug Henderson
2021-07-14 19:02 ` Achim Gratz
2021-07-14 19:59 ` Marco Atzeri
2021-07-14 21:08 ` Doug Henderson
2021-07-14 22:31 ` Ken Brown
2021-07-15 1:20 ` Doug Henderson
2021-07-15 11:57 ` Ken Brown
2021-07-15 16:04 ` Doug Henderson
2021-07-15 16:18 ` ASSI [this message]
2021-07-16 3:59 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fswfzh2q.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).