Answers inserted below... Le 16/10/2017 à 23:42, Noam Postavsky a écrit : > On Mon, Oct 16, 2017 at 1:11 PM, Vincent Belaïche > wrote: > >> I does not work for me if I don't change MSWindows PATH. But the text >> needs revision anyway because it does not say what has to be >> ensured. >> >> What happens for me is that c:\MSYS\INSTALL\DIR\msys64\mingw64\bin has >> to be high enough in the path list, otherwise Emacs gets frozen on >> start. >> >> I have not fully identified how high it has to be. It seems that if it >> is not before c:\Perl64\site\bin then the freeze happens (to be >> confirmed by more tests). c:\Perl64\site\bin is some ActiveState native >> perl implementation which contains a gcc.exe executable but no DLL's. > > I tried installing ActiveState perl, it adds this directory to PATH, > but the directory is empty (so of course there is no effect). Yes, this directory gets filled when you launch cpan, and install some module which I can't remember. Anyway, ActiveState is not to be blamed, I was a bit too quick in speculating that. After some dichotomy on the position of c:\msys64\mingw64\bin in the PATH I found that the conflict is with some c:\...\gtk\bin directory the content of which is as follows: --8<----8<----8<----8<----8<-- begin -->8---->8---->8---->8---->8---- c:\Nos_Programmes\gtk\bin>dir dir Le volume dans le lecteur C n’a pas de nom. Le numéro de série du volume est AC5E-0292 Répertoire de c:\Nos_Programmes\gtk\bin 18/05/2015 12:12 . 18/05/2015 12:12 .. 01/12/2013 14:25 24 525 autopoint 01/12/2013 14:38 1 538 croco-0.6-config 01/12/2013 14:25 143 837 envsubst.exe 01/12/2013 14:32 75 043 fc-cache.exe 01/12/2013 14:32 73 222 fc-cat.exe 01/12/2013 14:32 69 653 fc-list.exe 01/12/2013 14:32 71 841 fc-match.exe 01/12/2013 14:32 69 673 fc-pattern.exe 01/12/2013 14:32 68 340 fc-query.exe 01/12/2013 14:32 69 271 fc-scan.exe 01/12/2013 14:32 3 847 freetype-config 01/12/2013 14:31 1 380 gdbus-codegen 01/12/2013 14:31 105 157 gdbus.exe 01/12/2013 14:37 66 211 gdk-pixbuf-csource.exe 01/12/2013 14:37 64 161 gdk-pixbuf-pixdata.exe 01/12/2013 14:37 70 492 gdk-pixbuf-query-loaders.exe 01/12/2013 14:25 142 760 gettext.exe 01/12/2013 14:25 4 616 gettext.sh 01/12/2013 14:25 42 170 gettextize 01/12/2013 14:31 65 677 gio-querymodules.exe 01/12/2013 14:31 107 342 glib-compile-resources.exe 01/12/2013 14:31 118 257 glib-compile-schemas.exe 01/12/2013 14:31 90 048 glib-genmarshal.exe 01/12/2013 14:31 5 483 glib-gettextize 01/12/2013 14:31 17 968 glib-mkenums 01/12/2013 14:31 64 842 gobject-query.exe 01/12/2013 14:31 70 879 gresource.exe 01/12/2013 14:31 83 275 gsettings.exe 01/12/2013 14:31 66 125 gspawn-win64-helper-console.exe 01/12/2013 14:31 66 243 gspawn-win64-helper.exe 01/12/2013 15:05 68 226 gtk-query-immodules-3.0.exe 01/12/2013 15:05 99 034 gtk-update-icon-cache.exe 01/12/2013 15:05 585 gtk-update-icon-cache.exe.manifest 01/12/2013 15:05 192 548 gtk3-demo-application.exe 01/12/2013 15:05 516 715 gtk3-demo.exe 01/12/2013 15:05 145 457 gtk3-widget-factory.exe 01/12/2013 14:25 91 682 libasprintf-0.dll 01/12/2013 14:37 215 280 libatk-1.0-0.dll 01/12/2013 14:34 972 041 libcairo-2.dll 01/12/2013 14:34 73 310 libcairo-gobject-2.dll 01/12/2013 14:34 208 739 libcairo-script-interpreter-2.dll 01/12/2013 14:20 52 957 libcharset-1.dll 01/12/2013 14:38 338 000 libcroco-0.6-3.dll 01/12/2013 14:27 83 622 libffi-6.dll 01/12/2013 14:32 347 810 libfontconfig-1.dll 01/12/2013 14:32 752 539 libfreetype-6.dll 01/12/2013 15:05 93 389 libgailutil-3-0.dll 01/12/2013 15:05 870 852 libgdk-3-0.dll 01/12/2013 14:37 356 005 libgdk_pixbuf-2.0-0.dll 01/12/2013 14:25 1 401 627 libgettextlib-0-18-2.dll 01/12/2013 14:25 398 632 libgettextpo-0.dll 01/12/2013 14:25 320 913 libgettextsrc-0-18-2.dll 01/12/2013 14:31 1 789 609 libgio-2.0-0.dll 01/12/2013 14:31 1 513 572 libglib-2.0-0.dll 01/12/2013 14:31 64 399 libgmodule-2.0-0.dll 01/12/2013 14:31 403 969 libgobject-2.0-0.dll 01/12/2013 14:31 49 635 libgthread-2.0-0.dll 01/12/2013 15:05 6 317 774 libgtk-3-0.dll 01/12/2013 14:20 1 055 676 libiconv-2.dll 01/12/2013 14:25 154 337 libintl-8.dll 01/12/2013 14:35 449 890 libjasper-1.dll 01/12/2013 14:35 345 339 libjpeg-9.dll 01/12/2013 14:26 232 483 liblzma-5.dll 01/12/2013 14:35 439 347 libpango-1.0-0.dll 01/12/2013 14:35 142 951 libpangocairo-1.0-0.dll 01/12/2013 14:35 1 167 075 libpangoft2-1.0-0.dll 01/12/2013 14:35 147 550 libpangowin32-1.0-0.dll 01/12/2013 14:33 1 945 714 libpixman-1-0.dll 01/12/2013 14:32 2 348 libpng-config 01/12/2013 14:32 265 538 libpng15-15.dll 01/12/2013 14:32 2 348 libpng15-config 01/12/2013 15:07 362 691 librsvg-2-2.dll 01/12/2013 14:37 606 630 libtiff-5.dll 01/12/2013 14:27 1 740 678 libxml2-2.dll 01/12/2013 14:25 142 908 ngettext.exe 01/12/2013 14:35 72 342 pango-querymodules.exe 01/12/2013 14:35 121 526 pango-view.exe 01/12/2013 14:31 117 703 pkg-config.exe 01/12/2013 15:16 55 246 pthreadGC2.dll 01/12/2013 14:27 1 681 xml2-config 01/12/2013 14:27 145 311 xmllint.exe 01/12/2013 14:25 91 136 zlib1.dll 82 fichier(s) 29 471 245 octets 2 Rép(s) 101 430 677 504 octets libres --8<----8<----8<----8<----8<-- end -->8---->8---->8---->8---->8---- I can't remember when and why I installed this, but this is what causes the conflict, and placing c:\msys64\mingw64\bin just before it solves it, and apparently did not change anything for the application which I use on a regular basis. I have not investigated further which DLL in this directory is the conflict cause. What happens when PATH is incorrecly configured is that at Emacs start-up the Emacs windows appears, it remains black and everying is frozen (no keyboard events, no mouse event, to kill Emacs I need to go to the MSWindows Task manager). > >>> Is there some reason you changed to a for loop? >>> >> >> Yes, I had some packages already installed, and if I just type >> >> pacman -S msys/msys2-launcher-git \ >> msys/m4 \ >> msys/autoconf \ > [...] >> >> and I type ENTER for defaulting to « all » then it seems that pacman >> does not really re-install anything. With a look thing are handled one >> by one more cleanly, and it is easier for the user to discriminate. > > Yes, it seems that it hits an error trying to install > mingw64/mingw-w64-x86_64-liblcms2, and then just quits. The error is > somewhat lost in the noise: > > error: target not found: mingw-w64-x86_64-liblcms2 > > It seems the name must be updated to mingw-w64-x86_64-lcms2. I did that, and now it is fine w/o the loop. > > A drawback of the for loop method is that it is difficult to abort, > even hitting Ctrl+C doesn't stop the loop, you have to hit it again > for each package. OK. I attached a revised patch. I did not yet changed the section « ** Configure your MSYS2 PATH variable for application running from an mingw64 console ». I will do a further edit about that. This section will be renamed to « ** Check your MSYS2 PATH variable » and describe just the checking, and the bulk of the section about editing ~/.bashrc will be pushed to some « Trouble shooting » section, because, as I had written, the real problem was my improrer hacking of /msys2_sell.cmd & ~/.bashrc scripts. BTW, I have made one more comment to MSYS2 issue tracker with a revised MSYS2 launcher MSDos script fixing this PATH initialization issue caused by my previous hack: https://github.com/msys2/msys2/issues/71#issuecomment-337727083 I don't know whether MSYS2 people will buy that, now there is the launcher module. Yes, I still find that the MSDos script is useful for getting finer control/understanding about the launch. VBR, Vincent. --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus