From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin x86 on Windows 10 ARM64
Date: Wed, 11 Jul 2018 16:13:00 -0000 [thread overview]
Message-ID: <a2262d34-0a91-dcc5-3625-00ddd4e83311@SystematicSw.ab.ca> (raw)
In-Reply-To: <20180710130410.GL27673@calimero.vinschen.de>
On 2018-07-10 07:04, Corinna Vinschen wrote:
> On Jul 10 10:51, David Allsopp wrote:
>> I've been trying out the x86 emulation in Microsoft's ARM64 version of
>> Windows 10 1803.
>>
>> I had two issues with Cygwin x86. The first, which is simple, is that
>> Windows doesn't by default create C:\Windows\SysWOW64\drivers\etc which
>> causes /etc/postinstall/base-files-mketc.sh to exit with an error all the
>> time. I wonder if there's a possible workaround to make that less intrusive?
C:\ > mklink /d /h C:\Windows\SysWOW64\drivers\etc C:\Windows\System32\drivers\etc
Note: args reversed from ln
> Try if C:\Windows\Sysnative\drivers\etc works. That should be the
> easiest way to fix the issue in the script.
SysNative does not exist under x64 - could check arch dependent, or dir
dependent: check for hardcoded `cygpath -W`/SysNative/drivers/etc/ dir (unless
there is a standard SysNative folder id or env var I can't find), then fall back
to `cygpath -S`/drivers/etc/.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-07-11 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 9:51 David Allsopp
2018-07-10 13:04 ` Corinna Vinschen
2018-07-11 16:13 ` Brian Inglis [this message]
2018-07-12 11:04 ` David Allsopp
2018-07-12 12:04 ` Corinna Vinschen
2018-07-12 13:34 ` David Allsopp
2018-07-12 16:35 ` David Allsopp
2018-07-12 18:24 ` Corinna Vinschen
2018-07-10 17:12 ` Brian Inglis
2018-07-10 20:25 ` David Allsopp
2018-07-10 21:50 ` Andrey Repin
2018-07-11 8:14 ` Corinna Vinschen
2018-07-11 12:34 ` David Allsopp
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=a2262d34-0a91-dcc5-3625-00ddd4e83311@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).