From: tealhill <tealhill@gmail.com>
To: cygwin@cygwin.com
Subject: Please add /cygdrive/c/Windows/Sysnative to the default PATH
Date: Tue, 17 Nov 2020 14:54:48 -0500 [thread overview]
Message-ID: <rp19q9$12ic$1@ciao.gmane.io> (raw)
Dear all:
### Background information (you can skip this)
I use Pluckeye 0.99.60 for Windows. This is a self-control tool,
available online. It can help to stop me from visiting certain
time-wasting websites.
I also use Pluckeye's command-line component, pluck.exe. [I invoke the
tool from Bash 4.4.12. I'm running Bash on 32-bit Cygwin
3.1.7(0.340/5/3) on 64-bit Windows 10 build 19041.]
pluck.exe is a 64-bit tool, stored in C:\Windows\System32.
### The problem
32-bit tools, such as 32-bit Cygwin, don't usually see the real System32
directory. Instead, when they try to look inside System32, Windows
shows them the contents of a different directory, which contains only
32-bit System32 tools.
If 32-bit Cygwin needs to run a 64-bit tool, such as pluck.exe (from
Pluckeye) or wsl.exe (from the Windows Subsystem for Linux), it must
look in a different directory instead. It must look in
C:\Windows\Sysnative. In this virtual folder, 32-bit Cygwin can see all
the 64-bit System32 tools.
If you try to run pluck.exe without specifying that it's in
/cygdrive/c/Windows/Sysnative, you'll get the output:
[user@host ~]$ pluck
-bash: pluck: command not found
This 'virtual folder' stuff is non-obvious and confusing. It took me
some time to figure it all out.
### Proposed solution
Cygwin's /etc/profile sets the PATH.
Could /etc/profile please also add /cygdrive/c/Windows/Sysnative to the
end of the PATH?
### Conclusion
Thank you for reading this!
Also, I thank all of you who help out with the Cygwin project.
next reply other threads:[~2020-11-17 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 19:54 tealhill [this message]
2020-11-17 21:23 ` Thomas Wolff
2020-11-17 23:41 ` tealhill
2020-11-18 15:21 ` Bill Stewart
2020-11-18 15:45 ` Achim Gratz
2020-11-19 9:15 ` Andrey Repin
2020-11-19 15:57 ` Brian Inglis
2020-11-24 7:24 ` Thomas Wolff
2020-11-24 14:52 ` Bill Stewart
2020-11-24 15:10 ` Hamish McIntyre-Bhatty
2020-11-24 21:06 ` Brian Inglis
2020-11-24 1:58 ` L A Walsh
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='rp19q9$12ic$1@ciao.gmane.io' \
--to=tealhill@gmail.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).