X-Recipient: archive-cygwin AT delorie DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=BAYES_40,KAM_NUMSUBJECT,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 spammy=H*r:LOGIN, H*UA:16.0, H*x:16.0, H*F:D*ac.uk X-HELO: ppsw-32.csi.cam.ac.uk From: "David Allsopp" To: Subject: Cygwin x86 on Windows 10 ARM64 Date: Tue, 10 Jul 2018 10:51:00 +0100 Message-ID: <000b01d41833$948ec410$bdac4c30$@cl.cam.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: David Allsopp 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. The other is that all Cygwin binaries are emitting the "Could not compute FAST_CWD pointer" warning. Everything's up-to-date and I also tried it with the 2018-06-29 cygwin1.dll snapshot. Very happy to test things and poke around, I'd just need some pointers, if you'll excuse the pun. David -- 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