From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Issues with Cygwin64 on Windows11
Date: Sun, 31 Jul 2022 17:21:32 +0900 [thread overview]
Message-ID: <20220731172132.cf4d0a2d6acf2f6af96bb1c2@nifty.ne.jp> (raw)
In-Reply-To: <CAF9kqNEufMLALpfp-HwYaApoy=Y8ce2LBnD_YCY06YwEc_6guw@mail.gmail.com>
On Sun, 31 Jul 2022 09:11:17 +0300
Dimax wrote:
> Hello.
> I've never had much luck with Cygwin64 and used the 32 bit version before.
> Today I have no choice and I've installed Cyg64 on my new Win11 PC.
>
> Here is the first major issue I faced. I can not create symbolic links:
>
> Alex@Alexo ~
> $ ls /cygdrive/C/XOL/
>
> Alex@Alexo ~
> $ ln -s /cygdrive/C/XOL/ work
>
> Alex@Alexo ~
> $ ls -all work
> lrwxrwxrwx 1 Alex None 11 Jul 31 09:09 work -> /mnt/C/XOL/
>
> Alex@Alexo ~
> $ cd ~/work/
> -bash: cd: /home/Alex/work/: No such file or directory
>
> The link is created but I can not use it.
> The only thing that I did not standard was to call installation folder
> C:\Cygwin instead of default C:\Cygwin64
>
> Any help would be highly appreciated.
Thanks for the report. This seems to happen only when
the drive letter is uppercase.
ln -s /cygdrive/c/XOL/ work
works.
Anyway, I think this is a problem of cygwin1.dll.
This
work -> /mnt/C/XOL/
should be
work -> /cygdrive/C/XOL/
shouldn't it?
It guess this is a bug in the code added for WSL
compatibility.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-07-31 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 6:11 Dimax
2022-07-31 8:21 ` Takashi Yano [this message]
2022-08-01 0:23 ` Takashi Yano
2022-08-02 1:14 ` Ken Brown
2022-08-02 4:12 ` Takashi Yano
2022-08-02 8:19 ` Corinna Vinschen
2022-08-02 13:57 ` Ken Brown
2022-08-02 14:36 ` Corinna Vinschen
2022-08-02 14:39 ` Corinna Vinschen
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=20220731172132.cf4d0a2d6acf2f6af96bb1c2@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).