I've gotten Emacs to build under msys2; I'll look into providing an msys package for it.
In the process, I reinstalled msys2 several times, in order to avoid rebase issues I encountered. So I have some notes on improving http://sourceforge.net/p/msys2/wiki/MSYS2%20installation/ Is that page in a CM system? Perhaps I could use that to create a patch. In the meantime, some comments: I Downloading. It would help to clarify what 32-bit and 64-bit mean. They indicate what machine you are running on, not what machine you want to target. People building packages will often want to build a 32 bit program on a 64 bit machine (because the package has not yet been ported to 64 bit), and be confused by this choice (this happened to me). Perhaps something like: 1. 32-bit for a 32 bit host 2. 64 bit for a 64 bit host You can build and run 32 bit programs with the 64 bit install. When I ran the installer for the very first time, it somehow located my Cygwin HOME directory, and used the .bash_profile from there. That was very confusing, not to say disturbing. How did that happen? How can I prevent this on my next new Windows box? Restarting c:/msys64/msys64_shell.bat used the correct c:/msys64/home/stephe directory, and informed me that it was copying .bash_profile etc, as expected. However, later I deleted c:/msys64, and ran the installer again. It used the correct, but empty home directory, and _silently_ copied in the .bash_profile etc. It should have said it was doing the copy. I'm guessing the installer sets some state in the Windows Registry; is that documented somewhere, so I can delete it when I have problems installing in the future (things do change)? II updates and general package management Step 1 is simply wrong if the installer is older than the current central repository, which will normally be the case. The installer I used is dated 2014-07-04, and I had rebase problems with this command. I reinstalled several times, trying to find a sequence of updated package installations that did not report rebase problems. Below is what I came up with. It would help to separate the discussion of the issues from the recipe for upgrading. This is what I have in my notes: pacman maintains a local database of package versions. You have control over when that database is updated from the central repository. Running pacman can change dlls that are currently in use without checking, which can cause the post-install scripts to fail. This can happen any time you update the local package version database, since the central repository is updated often, and any new package you install may require an updated dll. During updating, kill the msys shell with the Windows X button immediately after running pacman; doing anything else in the shell after runnig pacman, including "exit", may run into the dll problem. To update safely: - exit all msys2 processes, start a new shell from Windows Explorer: c:\msys64\msys2_shell.bat - In the msys shell: $ pacman -Sy # updates local package database from central repository $ pacman -S --needed filesystem msys2-runtime libiconv \ libarchive libgpgme libcurl pacman ncurses libintl - from Windows Explorer: run c:\msys64\autorebase.bat run c:\msys64\msys2_shell.bat - In the msys shell: $ pacman -S --needed bash libreadline - from Windows Explorer: run c:\msys64\autorebase.bat run c:\msys64\msys2_shell.bat Since many (most? hopefully fewer as more prebuilt packages become available :) people installing msys2 will want to install a compiler in order to build packages, it would help to say how to do that simply: To install a standard set of development tools, including gcc for several languages: - for building 32 bit programs: $ pacman -S mingw-w64-i686-toolchain - for building 64 bit programs: $ pacman -S mingw-w64-X86_64-toolchain -- -- Stephe ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
