On Jul 11 00:36, Andrey Repin wrote: > 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. Did anybody notice my reply from 8 hours earlier? https://cygwin.com/ml/cygwin/2018-07/msg00091.html > 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 That would break existing scripts. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat