DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=ebYNG2kmUQ3NNab2
	F1tIWFkJyYm3YIUhIs8MbzcJ0WHlAwQ9zf71bXsE9GiQrly+OHOQ8/Ns5nXyVUI3
	rwwmAAfdLyy0TqsDl4AtLRySKX6y2WCQVeV6TuG5Ns5EI/w19Et2ShHunFt+hUt+
	RkvwpNqQMdHBa4cJ/jelFPwRFQ4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 11 Jul 2018 00:36:56 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <514216116.20180711003656@yandex.ru>
To: "David Allsopp" <David DOT Allsopp AT cl DOT cam DOT ac DOT uk>, cygwin AT cygwin DOT com
Subject: Re: Cygwin x86 on Windows 10 ARM64
In-Reply-To: <004401d4188c$17986b60$46c94220$@cl.cam.ac.uk>
References: <e4cb08a5-3db8-7a0b-edbd-de4fec1fc5fc AT SystematicSw DOT ab DOT ca>   <004401d4188c$17986b60$46c94220$@cl.cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, David Allsopp!

> Brian Inglis wrote:
>> On 2018-07-10 03: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?
>> > The error message implies that it may have computed the wrong
>> > directory, which it hasn't - it's just that the directory doesn't exist.
>> 
>> Do C:\Windows\{System32,SysNative,Sys*}\drivers\etc exist under the
>> emulator?
>> What does "cygpath -SU" show?

> cygpath -SU gives /proc/cygdrive/c/Windows/SysWOW64

> Checking within C:\Windows\SysWOW64\cmd.exe (i.e. x86 cmd):

> C:\Windows\System32\drivers\etc exists and contains expected files
> C:\Windows\Sysnative\drivers\etc exists and contains expected files (looks identical to System32, as you'd hope)
> C:\Windows\SysArm32\drivers does not contain an etc directory (but wasn't referenced)
> C:\Windows\SysWOW64\drivers didn't contain an etc directory (I created one to silence the error)

> So perhaps on WOW64 it would be worth falling back to Sysnative if etc
> isn't found? Or even just using Sysnative by default in WOW64?

I'd suggest using Sysnative unconditionally, and fall back to System32 if
Sysnative not found.

A better approach would be to make Cygwin trickery aware and just address real
directories instead of fake ones.
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365743.aspx


-- 
With best regards,
Andrey Repin
Wednesday, July 11, 2018 0:27:31

Sorry for my terrible english...


--
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