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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=hbAMbfag+8JQ3I+2QmSgMVzC3HiMBQ5BJ6P4XRB7zqh081ShM8DMV
	l3+H6ZE3YFtRqPxh9x2LOu7p+e3SuHLHYkca6/FPlxSU7mE54k8NZOixmjPdcDOH
	70Ecez2WGFxjY979EDyN+iFowbWvi0368eARcz+ftXdrrw3Lv4b2Ko=
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: Tue, 10 Jul 2018 15:04:10 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin x86 on Windows 10 ARM64
Message-ID: <20180710130410.GL27673@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <000b01d41833$948ec410$bdac4c30$@cl.cam.ac.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="E7i4zwmWs5DOuDSH"
Content-Disposition: inline
In-Reply-To: <000b01d41833$948ec410$bdac4c30$@cl.cam.ac.uk>
User-Agent: Mutt/1.9.2 (2017-12-15)

--E7i4zwmWs5DOuDSH
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
>=20
> 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 intrusi=
ve?

Try if C:\Windows\Sysnative\drivers\etc works.  That should be the
easiest way to fix the issue in the script.

> 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.
>=20
> The other is that all Cygwin binaries are emitting the "Could not compute
> FAST_CWD pointer" warning.

Nothing we can do about, unless somebody dives into assembler code on
such a system.  If the code switches to ARM64 early, this could be
tricky.

As a workaround I pushed a patch to check for running in WOW64 under
ARM64.  The warning is skipped then.  The already existing fallback
code should work most of the time.  Just give the latest developer
snapshot from https://cygwin.com/snapshots/ a try.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--E7i4zwmWs5DOuDSH
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAltErskACgkQ9TYGna5E
T6AO6A//ZPAD6E6FXslXNz+HT5SSeY7EDVvBduKqz5zBPuTnRgZRumZd41cjDHGa
WGU0kTG4lIiYWJAsfOypEsoPkPrJoJvgHDgyszc4sJt5Wz3nxhsBfm5hAcakzanD
39IKa2J+6mQmdHqcn3tATpjd5wIA48pdQtayuP0LzvPKKg8cg199S4/yiwMz9VJi
aWp1BtsDlQPDVcRq5zn2L6olqpZPD6DzEz7N5DpA0pTte/mzKrxZtnUDHnackIiZ
T7kjolvQDqNnMxuzDQuNtu+QZYDTbp1nrLlgZFsmgP6/brSaIPCceZjGrf3CiNU+
XI2CkjEO1y1u8P+AzGnae6Xg7eebUxNcYfOnyivD1v/VOT9VFmi7FCI1YFSPi8IL
8bxFtJMe8VKv0iEGvUSOQZKxX3RMqbH0iyPz34MYcKZBE8OHg5rx+ojhDOP/TD0X
iRIpvg3wQZenoERjh/V3CcCLSElnEi9pplhVpso8pgPLKp+GPD5mENLtIj5bzfOB
9FLZa3Xc0fv73k3xzMJDv7IbcDpOPoD9k2xAE274+Y0yu36XFcDguBoQjD31Vkis
TV0Xovu9oEs2Ap3hpTaBCuzrmfw8y1pY/GOCsaGxrzKUKULE2ugGnuQ9KMYr0VMv
DHzX6Ot0X1Jwl6oB565OQWlVmxIGmpME5/sv4l9bVdpsm+rqbcM=
=fAAW
-----END PGP SIGNATURE-----

--E7i4zwmWs5DOuDSH--