From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygwin1.dll > 3.1.4: Program execution fails if (WSL-)symlink exists and is present in PATH
Date: Wed, 2 Dec 2020 15:13:47 +0100 [thread overview]
Message-ID: <20201202141347.GR303847@calimero.vinschen.de> (raw)
In-Reply-To: <7c12fbc2-2d45-5b36-d31b-1bc0edc7fb7d@towo.net>
On Dec 2 15:07, Thomas Wolff wrote:
>
>
> Am 02.12.2020 um 15:05 schrieb Corinna Vinschen:
> > On Dec 2 13:39, Takashi Yano via Cygwin wrote:
> > > On Tue, 1 Dec 2020 19:13:39 -0500
> > > Ken Brown via Cygwin <cygwin@cygwin.com> wrote:
> > > > On 12/1/2020 4:24 AM, Mattl Mario wrote:
> > > > > Hello,
> > > > >
> > > > > Since cygwin1.dll version 3.1.5, I observed the following behavior:
> > > > > If a symbolic link is existing in the PATH environment, programs (external from Cygwin's system directory) using cygwin1.dll cannot be executed anymore.
> > > > > Possibly, because the Cygwin-DLL isn't found anymore.
> > > > >
> > > > > Steps to reproduce:
> > > > >
> > > > > cd /
> > > > > mkdir link_test
> > > > > cp /usr/bin/sed.exe link_test
> > > > > ln -s link_test test
> > > > > export PATH=/test:/link_test:/usr/bin:/bin
> > > > >
> > > > > /link_test/sed cannot be executed
> > > > > $ ldd /link_test/sed
> > > > > ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffffd960000)
> > > > > KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL (0x7ffffd140000)
> > > > > KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll (0x7ffffa8e0000)
> > > > > SYSFER.DLL => /cygdrive/c/WINDOWS/System32/SYSFER.DLL (0x550c0000)
> > > > >
> > > > > -> no cygwin- DLLs found
> > > > > [...]
> > > > I think this was fixed by commit 4b4fffe0f2390be6a5be27b6a3ceaa212a3724b2, but I
> > > > don't have time to check carefully, and I'm going to be AFK for a few days
> > > > starting tomorrow.
> > > I can reproduce this issue with current git head even with
> > > the commit 4b4fffe0f2390be6a5be27b6a3ceaa212a3724b2.
> > Just looking into it. It has something to do with missing to resolve
> > a WSL symlinks to a Windows path, but I'm not sure yet where this occurs.
> Actually I confirmed the issue too and I did not have to involve WSL, cygwin
> ln -s led to the behaviour.
WSL isn't involved, WSL symlinks (created by Cygwin) are.
Corinna
next prev parent reply other threads:[~2020-12-02 14:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 9:24 Mattl Mario
2020-12-02 0:13 ` Ken Brown
2020-12-02 4:39 ` Takashi Yano
2020-12-02 14:05 ` Corinna Vinschen
2020-12-02 14:07 ` Thomas Wolff
2020-12-02 14:13 ` Corinna Vinschen [this message]
2020-12-02 15:35 ` Corinna Vinschen
2020-12-03 9:30 ` Takashi Yano
2020-12-03 9:46 ` Corinna Vinschen
2020-12-03 10:58 Mattl Mario
2020-12-03 14:43 ` 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=20201202141347.GR303847@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).