public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Allsopp <David.Allsopp@cl.cam.ac.uk>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Cygwin x86 on Windows 10 ARM64
Date: Wed, 11 Jul 2018 12:34:00 -0000	[thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D901ADB433DA@Remus.metastack.local> (raw)
In-Reply-To: <20180711081443.GM27673@calimero.vinschen.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2386 bytes --]

Corinna Vinschen wrote:
> 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

Yes! I answered Brian's first because it didn't involve downloading anything, then I tried the snapshot you'd kindly provided - but it doesn't work, for weird reasons, and I'm still looking into exactly why in order to give a helpful reply as to why!

Sorry for the lag...


David
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

      reply	other threads:[~2018-07-11 12:34 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
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 [this message]

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=E51C5B015DBD1348A1D85763337FB6D901ADB433DA@Remus.metastack.local \
    --to=david.allsopp@cl.cam.ac.uk \
    --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).