bug#28888: 26.0.90; nt/INSTALL.W64

[Noam Postavsky <npostavs@users.sourceforge.net>]

[-- Attachment #1: Type: text/plain, Size: 22 bytes --]

[forwarding to list]


[-- Attachment #2: Type: message/rfc822, Size: 3345 bytes --]

From: Francis Wright <f.j.wright@live.co.uk>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Subject: RE: bug#28888: 26.0.90; nt/INSTALL.W64
Date: Wed, 18 Oct 2017 16:06:37 +0000
Message-ID: <DB6PR0901MB1638A2269F33044E72ACAF28E54D0@DB6PR0901MB1638.eurprd09.prod.outlook.com>

> From: Noam Postavsky [mailto:npostavs@gmail.com] On Behalf Of Noam
> Postavsky
> Sent: Wednesday, 18 October 2017 12:36 pm
> To: Francis Wright <f.j.wright@live.co.uk>
> Cc: 28888@debbugs.gnu.org
> Subject: Re: bug#28888: 26.0.90; nt/INSTALL.W64
>=20
> Francis Wright <f.j.wright@live.co.uk> writes:
>=20
> > I noticed the following errors in the 64-bit Windows build
> > instructions in the file nt/INSTALL.W64 when using a new MSYS2
> installation.
>=20
> There is some ongoing discussion on this in Bug#28601.
>=20
> > The library liblcms2 is not currently available using pacman, which
> > causes the pacman command shown to fail, but it works if that library
> > is removed. It might be best to recommend trying to install liblcms2
> > separately, in the hope that it will become available in the future.
>=20
> Actually, the package was just renamed to mingw-w64-x86_64-lcms2.
>=20
> https://debbugs.gnu.org/cgi/bugreport.cgi?users=3Demacs;bug=3D28601#77

OK, I'll try that when I build the next update. Thanks.

> > There is no file mingw64_shell.bat in the \msys64 folder. However,
> > there is an item labelled "MSYS2 MinGW 64-bit" in the Windows Start
> > menu, which seems to work correctly. Also, msys2_shell.bat is actually
> > msys2_shell.cmd.
>=20
> Can you check what that item links to?  I guess it should be
> C:\msys64\mingw64.exe (which is also one of the updates discussed in
> Bug#28601).
>=20
> https://debbugs.gnu.org/cgi/bugreport.cgi?users=3Demacs;bug=3D28601#29

"MSYS2 MinGW 64-bit" in my Windows Start menu is a shortcut to "C:\msys64\m=
sys2_shell.cmd -mingw64".

> > Apart from the above issues the build went well and the resulting
> > version of Emacs seems to have worked correctly so far.
>=20
> Did you change the Windows PATH?  The instructions currently suggest
> this, but it seems no longer needed for Emacs 26, and it causes some extr=
a
> complication with Msys find vs builtin Windows find.exe.
>=20
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D28601;filename=3DINSTALL.
> W64.diff;att=3D1;msg=3D65
> (near the bottom)

No, I didn't change the Windows path because I don't want this new MSYS env=
ironment to get mixed up with my normal environment. The build ran fine wit=
hout any modification to my path. The various options to start a MSYS shell=
 seem to set the path appropriately within that shell and Emacs runs fine f=
rom the shell. However, it doesn't find various required dlls when I run it=
 outside a MSYS shell and it requires more dlls than I had expected. The mo=
st obvious is libXpm-noX4.dll, but libgnutls-30.dll requires another 10 dep=
endent dlls! So a full set of dlls is going to be quite big.

Best wishes, Francis