{"id":5035,"date":"2016-08-19T09:17:59","date_gmt":"2016-08-19T09:17:59","guid":{"rendered":"http:\/\/blog.bachi.net\/?p=5035"},"modified":"2021-05-12T16:16:34","modified_gmt":"2021-05-12T16:16:34","slug":"msys2","status":"publish","type":"post","link":"https:\/\/blog.bachi.net\/?p=5035","title":{"rendered":"MSYS2 \/ mingw-w64-x86_64"},"content":{"rendered":"

MSYS2 introduction<\/a>
\nMSYS2 Wiki<\/a><\/p>\n

MSYS2 vs. MinGw64<\/h3>\n

MSYS vs. MinGW: internal environment variables<\/a><\/p>\n

\r\n$ uname\r\nMSYS_NT-10.0\r\n\r\n$ uname\r\nMINGW64_NT-10.0\r\n<\/pre>\n
Package Manager<\/h3>\n
\r\n$ pacman -Q\r\n<list all packages>\r\n\r\n$ pacman -Qi <package>\r\n<info about a single package>\r\n\r\n$ pacman -Ql <package>\r\n<files of a single package>\r\n<\/pre>\n
Pin to Taskbar<\/h3>\n
\r\n$ pacman -S msys2-launcher\r\n\r\n$ pacman -Qi msys2-launcher\r\nName            : msys2-launcher-git\r\nVersion         : 0.3.32.56c2ba7-2\r\nDescription     : Helper for launching MSYS2 shells\r\nArchitecture    : x86_64\r\nURL             : None\r\nLicenses        : MIT\r\nGroups          : base\r\nProvides        : msys2-launcher\r\nDepends On      : mintty>=1~2.2.1\r\nOptional Deps   : None\r\nRequired By     : None\r\nOptional For    : None\r\nConflicts With  : msys2-launcher\r\nReplaces        : None\r\nInstalled Size  : 157.00 KiB\r\nPackager        : Alexey Pavlov <alexpux@gmail.com>\r\nBuild Date      : Wed, Sep 7, 2016 7:59:07 PM\r\nInstall Date    : Thu, Apr 18, 2019 9:46:39 PM\r\nInstall Reason  : Explicitly installed\r\nInstall Script  : No\r\nValidated By    : Signature\r\n\r\n$ pacman -Ql msys2-launcher\r\nmsys2-launcher-git \/mingw32.exe\r\nmsys2-launcher-git \/mingw32.ini\r\nmsys2-launcher-git \/mingw64.exe\r\nmsys2-launcher-git \/mingw64.ini\r\nmsys2-launcher-git \/msys2.exe\r\nmsys2-launcher-git \/msys2.ini\r\n<\/pre>\n
Update<\/h3>\n
MinGW coding under Windows (C, C++, OpenMP, MPI)<\/a>
\nopenFrameworks: msys2<\/a><\/p>\n
\r\n$ pacman -Syu\r\n$ pacman -Su\r\n$ pacman -S base-devel\r\n$ pacman -S mingw-w64-x86_64-toolchain\r\n$ pacman -S git\r\n<\/pre>\n
fwrite()<\/h3>\n
fwrite() c function writing extra bytes<\/a>
\nThe difference in File access mode “w” and “wb”<\/a><\/p>\n
\r\n\/\/ linux doesn't care... but windows does!\r\n\r\nFILE *fp = fopen(filename, "w"); \/\/ text mode\r\n\/\/ if streams includes 0x0A (\\n) it prepends it with 0x0D (\\r)\r\n\r\nFILE *fp = fopen(filename, "wb"); \/\/ binary mode\r\n<\/pre>\n
Keyring<\/h3>\n
2020-06-29 – new packagers<\/a><\/p>\n
Problem<\/h4>\n
\r\n$ pacman -Syu\r\n:: Synchronizing package databases...\r\n mingw32 \r\n mingw32.sig\r\nerror: mingw32: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown\r\nerror: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" could not be looked up remotely\r\nerror: failed to update mingw32 (invalid or corrupted database (PGP signature))\r\n mingw64\r\n mingw64.sig\r\nerror: mingw64: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown\r\nerror: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" could not be looked up remotely\r\nerror: failed to update mingw64 (invalid or corrupted database (PGP signature))\r\n msys\r\n msys.sig\r\nerror: msys: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown\r\nerror: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" could not be looked up remotely\r\nerror: failed to update msys (invalid or corrupted database (PGP signature))\r\nerror: failed to synchronize all databases\r\n<\/pre>\n
Solution<\/h4>\n
\r\n# rm -r \/etc\/pacman.d\/gnupg\/\r\n# pacman-key --init\r\n# pacman-key --populate msys2\r\n\r\n$ curl -O http:\/\/repo.msys2.org\/msys\/x86_64\/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz\r\n$ curl -O http:\/\/repo.msys2.org\/msys\/x86_64\/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig\r\n\r\n# pacman -U --config <(echo) msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz\r\n\r\n$ pacman -Syu\r\n:: Synchronizing package databases...\r\n mingw32 is up to date\r\n mingw64 is up to date\r\n msys is up to date\r\n:: Starting core system upgrade...\r\n[...]\r\n<\/pre>\n
arm-none-eabi<\/h3>\n
mingw-w64-arm-none-eabi-newlib<\/a>
\nMINGW-packages wiki<\/a>
\nMSYS2-packages<\/a><\/p>\n
arm-none-eabi GCC toolchain<\/a><\/p>\n
\r\n$ git clone https:\/\/github.com\/Alexpux\/MINGW-packages.git\r\n$ cd ~\/MINGW-packages\/mingw-w64-arm-none-eabi-binutils\/\r\n$ MINGW_INSTALLS=mingw64 makepkg-mingw -sLf\r\n$ pacman -U mingw-w64-x86_64-arm-none-eabi-binutils-2.24-1-any.pkg.tar.xz\r\n\r\n$ cd ~\/MINGW-packages\/mingw-w64-arm-none-eabi-gcc\/\r\n$ MINGW_INSTALLS=mingw64 makepkg-mingw -sLf\r\n==> Making package: mingw-w64-gcc 4.8.4-1 (Sun, Mar  5, 2017  9:50:40 AM)\r\n==> Checking runtime dependencies...\r\n==> Installing missing dependencies...\r\nerror: target not found: mingw-w64-x86_64-arm-none-eabi-newlib\r\n==> ERROR: 'pacman' failed to install missing dependencies.\r\n\r\n$ cd ~\/MINGW-packages\/mingw-w64-arm-none-eabi-newlib\/\r\n$ MINGW_INSTALLS=mingw64 makepkg-mingw -sLf\r\n==> Making package: mingw-w64-newlib 2.1.0-1 (Sun, Mar  5, 2017  9:51:25 AM)\r\n==> Checking runtime dependencies...\r\n==> Checking buildtime dependencies...\r\n==> Retrieving sources...\r\n[...]\r\n\/bin\/sh ..\/..\/gcc\/gcc\/..\/move-if-change tmp-mlib.h multilib.h\r\necho timestamp > s-mlib\r\nrm cpp.pod gcov.pod fsf-funding.pod gfdl.pod\r\nmake[1]: Leaving directory '\/home\/bachman0\/MINGW-packages\/mingw-w64-arm-none-eabi-newlib\/src\/build-gcc-x86_64-w64-mingw32\/gcc'\r\nmake: *** [Makefile:3892: all-gcc] Error 2\r\n==> ERROR: A failure occurred in prepare().\r\n    Aborting...\r\n<\/pre>\n
List of files installed by a package<\/h3>\n
\r\n$ pacman -Ql mingw-w64-x86_64-arm-none-eabi-binutils\r\n[...]\r\nmingw-w64-x86_64-arm-none-eabi-binutils \/mingw64\/bin\/arm-none-eabi-addr2line.exe\r\nmingw-w64-x86_64-arm-none-eabi-binutils \/mingw64\/bin\/arm-none-eabi-ar.exe\r\nmingw-w64-x86_64-arm-none-eabi-binutils \/mingw64\/bin\/arm-none-eabi-as.exe\r\nmingw-w64-x86_64-arm-none-eabi-binutils \/mingw64\/bin\/arm-none-eabi-ld.exe\r\nmingw-w64-x86_64-arm-none-eabi-binutils \/mingw64\/bin\/arm-none-eabi-objcopy.exe\r\nmingw-w64-x86_64-arm-none-eabi-binutils \/mingw64\/bin\/arm-none-eabi-objdump.exe\r\nmingw-w64-x86_64-arm-none-eabi-binutils \/mingw64\/bin\/arm-none-eabi-readelf.exe\r\nmingw-w64-x86_64-arm-none-eabi-binutils \/mingw64\/bin\/arm-none-eabi-strip.exe\r\n[...]\r\n<\/pre>\n
MSYS2 consists of three subsystems and their corresponding package repositories, msys2<\/code><\/strong>, mingw32<\/code><\/strong>, and mingw64<\/code><\/strong>.<\/p>\n
The mingw<\/code><\/strong> subsystems provide native Windows programs and are the main focus of the project. These programs are built to co-operate well with other Windows programs, independently of the other subsystems.<\/p>\n
The msys2<\/code><\/strong> subsystem provides an emulated mostly-POSIX-compliant environment for building software, package management, and shell scripting. These programs live in a virtual single-root filesystem (the root is the MSYS2 installation directory). Some effort is made to have the programs work well with native Windows programs, but it’s not seamless.<\/p>\n
Each of the subsystems provides its own native (i.e. target=host) compiler toolchain, in msys2-devel<\/code><\/strong>, mingw-w64-i686-toolchain<\/code><\/strong>, and mingw-w64-x86_64-toolchain<\/code><\/strong>. There are also cross compiler toolchains with host={i686,x86_64}-pc-msys<\/code> and target={i686,x86_64}-w64-mingw32<\/code> in mingw-w64-cross-toolchain<\/code><\/strong>, but these are of limited use because there are no library packages for them.<\/p>\n
Every subsystem has an associated “shell”, which is essentially a set of environment variables that allow the subsystems to co-operate properly. These shells can be invoked using scripts in the MSYS2 installation directory or shortcuts in the Start menu. The scripts set the MSYSTEM variable and start a terminal emulator with bash. Bash in turn sources \/etc\/profile<\/code> which sets the environment depending on the value of MSYSTEM.<\/p>\n
Update MSYS2<\/h3>\n
ssh not finding ssh config or IdentityFile<\/a><\/p>\n
\r\n$ pacman -Sy\r\n:: Synchronisiere Paketdatenbanken...\r\n mingw32                  291,3 KiB   867K\/s 00:00 [#####################] 100%\r\n mingw32.sig               96,0   B  0,00B\/s 00:00 [#####################] 100%\r\n mingw64                  290,9 KiB  1672K\/s 00:00 [#####################] 100%\r\n mingw64.sig               96,0   B  0,00B\/s 00:00 [#####################] 100%\r\n msys                     135,6 KiB  11,0M\/s 00:00 [#####################] 100%\r\n msys.sig                  96,0   B  0,00B\/s 00:00 [#####################] 100%\r\n\r\n$ pacman --needed -S bash pacman msys2-runtime\r\n(1\/3) Aktualisiere msys2-runtime                   [#####################] 100%\r\n(2\/3) Aktualisiere bash                            [#####################] 100%\r\n(3\/3) Aktualisiere pacman                          [#####################] 100%\r\n\r\n$ exit\r\n\r\n$ pacman -Su\r\n:: Starting core system upgrade...\r\n[...]\r\n      WARNING: the shell starting scripts have been unified. Please update your\r\n      shortcuts to the following targets, otherwise they will STOP WORKING:\r\n\r\n          * MSYS2_ROOT\\msys2_shell.cmd -mingw32\r\n          * MSYS2_ROOT\\msys2_shell.cmd -mingw64\r\n          * MSYS2_ROOT\\msys2_shell.cmd -msys\r\n[...]\r\n\r\n$ exit\r\nUpdate Links => .bat to .cmd\r\n\r\n$ pacman -S openssh\r\n$ pacman -S git\r\n\r\n$ pacman -h -S\r\nVerwendung:  pacman {-S --sync} [Optionen] [Paket(e)]\r\nOptionen:\r\n  -b, --dbpath <Pfad>  Setzt einen anderen Ort f\u00fcr die Datenbank\r\n  -c, --clean          Entfernt alte Pakete aus dem Paketpuffer (-cc f\u00fcr alle)\r\n  -d, --nodeps         \u00dcberspringt die Versions\u00fcberpr\u00fcfungen f\u00fcr Abh\u00e4ngigkeiten (-dd um alle \u00dcberpr\u00fcfungen zu \u00fcberspringen)\r\n  -g, --groups         Zeigt alle Mitglieder einer Paket-Gruppe an\r\n                       (-gg um alle Gruppen samt Mitgliedern anzuzeigen)\r\n  -i, --info           Zeigt Paketinformationen an (-ii f\u00fcr erweiterte Informationen)\r\n  -l, --list <repo>    Zeigt eine Liste aller Pakete eines Repositoriums an\r\n  -p, --print          Zeigt die Ziele an, statt die Operation auszuf\u00fchren\r\n  -q, --quiet          Zeigt weniger Information bei Abfragen und Suche an\r\n  -r, --root <Pfad>    Setzt ein alternatives Wurzelverzeichnis zur Installation\r\n  -s, --search <regex> Durchsucht entfernte Repositorien nach einem Wort\r\n  -u, --sysupgrade     Aktualisiert installierte Pakete (-uu erm\u00f6glicht Downgrades)\r\n  -v, --verbose        Sei gespr\u00e4chig\r\n  -w, --downloadonly   L\u00e4dt Pakete herunter, ohne etwas zu installieren oder aktualisieren\r\n  -y, --refresh        L\u00e4dt aktuelle Paketdatenbanken vom Server herunter\r\n                       (-yy um eine Aktualisierung auch bei aktuellen Datenbanken durchzuf\u00fchren)\r\n      --arch <arch>    Setzt eine alternative Architektur\r\n      --asdeps         Installiert Pakete als nicht-ausdr\u00fccklich installiert\r\n      --asexplicit     Installiert Pakete als ausdr\u00fccklich installiert\r\n      --assume-installed <package=version>\r\n                       F\u00fcgt ein virtuelles Paket hinzu, um Abh\u00e4ngigkeiten zu erf\u00fcllen\r\n      --cachedir <Verzeichnis>  Setzt einen anderen Ort f\u00fcr den Paketpuffer\r\n      --color <wann>   Ausgabe farbig darstellen\r\n      --config <Pfad>  Setzt eine alternative Konfigurationsdatei\r\n      --confirm        Immer nach einer Best\u00e4tigung fragen\r\n      --dbonly         Ver\u00e4ndert nur Datenbank-Eintr\u00e4ge, keine Paketdateien\r\n      --debug          Zeigt Debug-Meldungen an\r\n      --force          Installation erzwingen, Dateikonflikte \u00fcberschreiben\r\n      --gpgdir <path>  Setzt alternatives Konfigurationsverzeichnis f\u00fcr GnuPG\r\n--hookdir <dir> setze ein anderes Hook-Verzeichnis\r\n      --ignore <pkg>   Ignoriert ein neues Paket (kann mehrfach genutzt werden)\r\n      --ignoregroup <grp>\r\n                       Ignoriert Upgrade einer Gruppe (kann mehrfach genutzt werden)\r\n      --logfile <Pfad> Setzt eine alternative Log-Datei\r\n      --needed         Installiert aktuelle Pakete nicht erneut\r\n      --noconfirm      Niemals nach einer Best\u00e4tigung fragen\r\n      --noprogressbar  Keine Fortschrittsanzeige anzeigen, wenn Dateien heruntergeladen werden\r\n      --noscriptlet    Installationsskript nicht ausf\u00fchren, falls vorhanden\r\n      --print-format <string>\r\n                       Legt fest, wie die Ziele ausgegeben werden sollen\r\n\r\n<\/pre>\n
C:\\msys64\\msys2_shell.bat’ is not recognized as an internal or external command<\/h3>\n
Current installer\/installation instructions are broken<\/a>
\n==> update links. Don’t use msys2_shell.bat but msys2_shell.cmd<\/p>\n
Install Python NumPy<\/h3>\n
Practical Computing for Biologists – Setting up Windows and Linux<\/a><\/p>\n
\r\n# download MSYS2 (Arch Linux)\r\nhttps:\/\/msys2.github.io\/\r\n# Choose the version that says x86_64, not i686\r\n \r\n# Update system\r\npacman --needed -Sy bash pacman pacman-mirrors msys2-runtime\r\n \r\n# Restart MSYS \r\n# (Close all windows and reopen from start menu)\r\n# All Programs > MSYS2 64-bit > MSYS Shell\r\n \r\npacman -Su\r\n \r\n# You might get some errors. If so, just run the command again and it should pick up the slack.\r\n \r\n#install python and other utilities\r\n# REQUIRED\r\npacman --noconfirm -S  gcc python2 man nano sqlite vim git bc tar \r\n \r\n# This can take a while to download\r\n \r\n# Note: To search for other package locations, use\r\n \r\n    pacman -Ss <package_name>\r\n \r\nThen to install, copy the name (before the version number) after a pacman -Sy command...\r\n \r\n \r\n# issues: sudo and screen not there in default pacman...\r\n \r\n# NEXT you should do these commands:\r\ncd \/usr\/bin\r\nln -sf python2 python\r\ncd\r\n \r\n# Then install pip using these steps:\r\n \r\nmkdir ~\/scripts\r\ncd ~\/scripts\r\ncurl -O 'https:\/\/bootstrap.pypa.io\/get-pip.py'\r\n.\/get-pip.py\r\n \r\n# If that succeeds (which pip should now find something)\r\nthen..\r\n \r\n  rm get-pip.py\r\n \r\n# Now to use the installer for grabbing python packages like numpy, Biopython, and beautifulSoup:\r\n \r\n   pip install numpy\r\n \r\n##########################\r\nWorking in MSYS2\r\n \r\nYour home directory, as we refer to it in the book, will be \/home\/lucy in the terminal window, but it lives in the c:\\msys32 (or msys64) folder. You could make a shortcut from the folder here with our username to the Windows desktop for easy cross-platform access.\r\n \r\n# MSYS2 starts with an annoying multi-line prompt, so edit your .bash_profile using this command\r\n \r\n    nano ~\/.bash_profile\r\n \r\n# Note that <ctrl>C will not work for copying in the terminal, because it has another function.\r\n# Right click to copy\/paste from the pop-up menu\r\n \r\n# Add the following four lines to your .bash_profile\r\n \r\nPS1='\\[\\e[1;32m\\]\\u:\\[\\e[1;36m\\]\\w \\$ \\e[0m'\r\nexport PATH=$PATH:$HOME\/scripts\r\nexport EDITOR=\/usr\/bin\/nano\r\nset -o noclobber\r\n \r\n################################\r\n \r\nNext, in Windows, install the GUI\r\nInstall <a href="http:\/\/www.sublimetext.com\/3">Sublime Text 3<\/a>\r\n \r\nAfter installation, Change color scheme to iPlastic\r\n \r\nTo get the command-line option (so you can edit files from the terminal by typing 'subl' google the page about changing your System Path to work with Sublime Text 3.\r\n##############################\r\n<\/pre>\n
Difference between native python and mingw-w64 python.<\/a>
\nNumpy Mingw w64 FAQ<\/a>
\nAnaconda – open data science platform<\/a>
\nConda – open source package management system<\/a><\/p>\n
Install mingw-w64-x86_64 packages<\/h3>\n
\r\n$ pacman -S mingw-w64-x86_64-python3\r\n[...]\r\n(24\/24) checking for file conflicts                                                                                 [####################################################################] 100%\r\nerror: failed to commit transaction (conflicting files)\r\nmingw-w64-x86_64-gmp: \/mingw64 exists in filesystem\r\n[...]\r\n<\/pre>\n
Msys2 + Windows 10 + pacman errors <\/a><\/p>\n
\r\n$ mkdir \/mingw64\r\n<\/pre>\n
Change language<\/h3>\n
\r\n$ export LC_ALL=en_US.UTF-8\r\n<\/pre>\n
No C Compiler installed<\/h3>\n
\r\n$ python3 setup.py install\r\nrunning install\r\nrunning build\r\nrunning build_py\r\ncreating build\r\ncreating build\/lib.mingw-3.5\r\ncreating build\/lib.mingw-3.5\/bigfloat\r\ncopying bigfloat\/context.py -> build\/lib.mingw-3.5\/bigfloat\r\ncopying bigfloat\/core.py -> build\/lib.mingw-3.5\/bigfloat\r\ncopying bigfloat\/ieee.py -> build\/lib.mingw-3.5\/bigfloat\r\ncopying bigfloat\/rounding_mode.py -> build\/lib.mingw-3.5\/bigfloat\r\ncopying bigfloat\/__init__.py -> build\/lib.mingw-3.5\/bigfloat\r\ncreating build\/lib.mingw-3.5\/bigfloat\/test\r\ncopying bigfloat\/test\/test_bigfloat.py -> build\/lib.mingw-3.5\/bigfloat\/test\r\ncopying bigfloat\/test\/test_context.py -> build\/lib.mingw-3.5\/bigfloat\/test\r\ncopying bigfloat\/test\/test_mpfr.py -> build\/lib.mingw-3.5\/bigfloat\/test\r\ncopying bigfloat\/test\/test_rounding_mode.py -> build\/lib.mingw-3.5\/bigfloat\/test\r\ncopying bigfloat\/test\/test___all__.py -> build\/lib.mingw-3.5\/bigfloat\/test\r\ncopying bigfloat\/test\/__init__.py -> build\/lib.mingw-3.5\/bigfloat\/test\r\nrunning build_ext\r\nTraceback (most recent call last):\r\n  File "setup.py", line 267, in <module>\r\n    'bigfloat.test',\r\n  File "C:\/msys64\/mingw64\/lib\/python3.5\\distutils\\core.py", line 148, in setup\r\n    dist.run_commands()\r\n  [...]\r\n  File "C:\/msys64\/mingw64\/lib\/python3.5\\distutils\\ccompiler.py", line 1033, in new_compiler\r\n    return klass(None, dry_run, force)\r\n  File "C:\/msys64\/mingw64\/lib\/python3.5\\distutils\\cygwinccompiler.py", line 288, in __init__\r\n    CygwinCCompiler.__init__ (self, verbose, dry_run, force)\r\n  File "C:\/msys64\/mingw64\/lib\/python3.5\\distutils\\cygwinccompiler.py", line 127, in __init__\r\n    if self.ld_version >= "2.10.90":\r\nTypeError: unorderable types: NoneType() >= str()\r\n\r\n$ pacman -S mingw-w64-x86_64-gcc\r\n\r\n$ python3 setup.py install\r\nrunning install\r\nrunning build\r\nrunning build_py\r\nrunning build_ext\r\nbuilding 'mpfr' extension\r\ncreating build\/temp.mingw-3.5\r\nC:\\msys64\\mingw64\\bin\/x86_64-w64-mingw32-gcc.exe -Wno-unused-result -Wsign-compare -DNDEBUG -march=x86-64 -mtune=generic -O2 -pipe -fwrapv -D__USE_MINGW_ANSI_STDIO=1 -DNDEBUG -IC:\/msys64\/mingw64\/include\/python3.5m -c mpfr.c -o build\/temp.mingw-3.5\/mpfr.o\r\n[...]\r\nWriting C:\/msys64\/mingw64\/lib\/python3.5\/site-packages\/bigfloat-0.3.0-py3.5.egg-info\r\n\r\n<\/pre>\n
pacman install build system for mingw-w64-x86_64<\/h3>\n
\r\n$ pacman -S mingw-w64-x86_64-gcc\r\n$ pacman -S mingw-w64-x86_64-gdb\r\n<\/pre>\n
pacman query<\/h3>\n
How can I show the list of all installed packages in Arch Linux (pacman packet manager)?<\/a><\/p>\n
\r\n       -Q, --query\r\n           Query the package database.\r\n           This operation allows you to view installed packages\r\n           and their files, as well as meta-information about\r\n           individual packages\r\n       -i, --info\r\n           Display information on a given package. \r\n       -s, --search <regexp>\r\n           Search each locally-installed package for names or\r\n           descriptions that match regexp.\r\n<\/pre>\n
\r\n$ pacman -Qi mingw-w64-x86_64-python3\r\nName                     : mingw-w64-x86_64-python3\r\nVersion                  : 3.5.2-2\r\n\r\n$ pacman -Qs python\r\nlocal\/mingw-w64-x86_64-python3 3.5.2-2\r\n    A high-level scripting language (mingw-w64)\r\nlocal\/mingw-w64-x86_64-python3-cairo 1.10.0-5\r\n    Python2 bindings for the cairo graphics library (mingw-w64)\r\nlocal\/mingw-w64-x86_64-python3-cycler 0.9.0-1\r\n    Composable style cycles\r\n\r\n[...]\r\n<\/pre>\n
\r\n$ pacman -Ss xpdf\r\nmingw32\/mingw-w64-i686-poppler 0.76.1-1\r\n    PDF rendering library based on xpdf 3.0 (mingw-w64)\r\nmingw32\/mingw-w64-i686-xpdf 4.00-1\r\n    Utilities for PDF files (mingw-w64)\r\nmingw64\/mingw-w64-x86_64-poppler 0.76.1-1\r\n    PDF rendering library based on xpdf 3.0 (mingw-w64)\r\nmingw64\/mingw-w64-x86_64-xpdf 4.00-1\r\n    Utilities for PDF files (mingw-w64)\r\n[...]\r\n<\/pre>\n
\r\n$ pacsearch python2\r\n<\/pre>\n
\r\n$ pacman -R mingw-w64-x86_64-arm-none-eabi-binutils\r\n<\/pre>\n
MSYS2 Shell vs MinGW-w64 Shell<\/h1>\n
MSYS2 Shell or MinGW-w64 Shell<\/a>
\nMSYS2-Introduction<\/a>
\nHow does MSYS2 differ from Cygwin?<\/a><\/p>\n
MSYS2<\/h3>\n
MSYS2 is based on Cygwin and knows how to understand POSIX conventions like paths (\/usr\/bin\/<\/code>, \/etc<\/code>) as well as special devices like \/dev\/null<\/code>, \/dev\/clipboard<\/code>, etc and many other things. MSYS2 comes with a GCC toolchain who will produce native binaries that are always tied to msys-2.0.dll<\/code>. It’s that DLL that does all the magic of interoperability between POSIX conventions and Windows. It’s because of it that it’s possible to use a Unix like path \/home\/joe\/<\/code> and pass it to a Windows and it still works.<\/p>\n
Indeed, (I’m not sure of the exact details) but when when msys-2.0.dll<\/code>
\nsees you are calling a native Windows executables (one that does not
\ndepends on msys-2.0.dll<\/code>), it will convert the path \/home\/joe\/<\/code> to a
\nWindows path like C:\\Users\\joe<\/code> that the native Windows program receives
\nand knows how to understand. Without this translation, the Windows program
\nwould receive \/home\/joe\/<\/code> and wouldn’t understand how to treat it
\ncorrectly. All this paths translations applies also to environment
\nvariables.<\/p>\n
This process (and all the POSIX emulation layer) incurs a performance
\npenalty that can be significant for heavy file-centric software. Git is a
\ngood example and that’s why the MSYS2 git package (msys\/git<\/code>) is slower
\nthan a native git client like the one provided by Git For Windows
\n(git-for-windows\/mingw-w64-x86_64-git<\/code>). That’s why a native program (read
\na MINGW one) is usually “better” than an MSYS2 one. Don’t be afraid of
\nusing pure MSYS2 program, in most cases (I would say 90%), the difference
\nis not significant because bottleneck is not the filesystem (CPU, network,
\nother).<\/p>\n
That’s why you will often read that MSYS2 is only a way to make it easier
\nto build and deploy MINGW native executables. In my personal opinion and
\nthe way I use it, it’s much much more than that as I use and build little
\nMINGW tools. MSYS2 is a full subsystem dealing with way more than just a
\ntoolchain as it deals with filesystem, users, permissions (to an extent)
\nand much more. I use it mainly because it has the same toolset as the one
\nI’m used on Linux (console-based of course :)).<\/p>\n
Because MSYS2 understands POSIX and has a pretty good emulation layer, it
\nis often very easy to port a package originally built on Linux to it,
\nbecause almost no code work is needed.<\/p>\n
MINGW<\/h3>\n
MINGW (either 32 or 64) is a set of toolchain to build native Windows
\nprogram. Those program do not depends on msys-2.0.dll<\/code> and depends rather
\non MSVC runtime. Those don’t understand POSIX paths, so if you pass
\n\/home\/joe<\/code> outside of an MSYS2 shells (from pure cmd for example), it will
\nnot understand it. Indeed, in pure cmd <\/code>(and via many interactions from
\nother programs), no translation of paths is performed.<\/p>\n
MINGW toolchains are based on mingw-w64 which
\nprovides the ground work to compile them. They are available in pacman for
\ninstallation and they also contains GCC et related tools (binutils, ld).
\nWhen invoked, GCC produces pure native executable. So, when working with a
\nMINGW program, remember that it’s like a native Window program that knows
\nnothing about MSYS2.<\/p>\n
MSYS2 happens to actual provides those toolchains directly to you
\npre-compiled via pacman. Note however, that it’s possible to download the
\nmingw-w64 toolchains in standalone, put them somewhere and invoke them
\nafterward in MSYS2 (by proprely configuring PATH and other variables
\nyourself). They can also be invoked via cmd <\/code>directly because they do not
\ndepend on MSYS2 at all.<\/p>\n
Shells<\/h3>\n
When you start any of the MSYS2 shells, they all start an MSYS2 bash<\/code>
\nprogram. Since it’s a MSYS2 bash<\/code>, it understands Unix paths and will do
\ntranslation when calling native Windows executables.<\/p>\n
That being said, what is the difference between all the shells? It all
\nabout the tweaking some environment variables to change default programs
\npicked when calling them. It’s mainly about the PATH environment variable
\nbut it also involves MSYSTEM PKG_CONFIG_PATH ACLOCAL_PATH MANPATH like Ray
\nsaid earlier. Checkout \/etc\/profile<\/code> around line 28 to see the conditional
\nthat sets all this.<\/p>\n
Let’s assume you have installed three toolchains:
\n* MSYS2 (package group msys2-devel<\/code>) to compile MSYS2 tools which
\ninstalls gcc in \/usr\/bin<\/code>.
\n* MINGW32 (package group mingw-w64-i686-toolchain<\/code>) to compile Windows
\nnative 32 bits executable which installs gcc in \/mingw32\/bin<\/code>.
\n* MINGW64 (package group mingw-w64-x86_64-toolchain<\/code>) to compile
\nWindows native 64 bits executable which installs gcc in \/mingw64\/bin<\/code>.<\/p>\n
For msys2_shell, PATH is roughly only \/usr\/local\/bin:\/usr\/bin:\/bin<\/code>. This
\nmeans that when running gcc<\/code>, you will get \/usr\/bin\/gcc<\/code>.<\/p>\n
For mingw32_shell, PATH is roughly
\n\/mingw32\/bin:\/usr\/local\/bin:\/usr\/bin:\/bin<\/code>. This means that now, running
\ngcc <\/code>you will get instead \/mingw32\/bin\/gcc<\/code>.<\/p>\n
For mingw64_shell, PATH is roughly
\n\/mingw64\/bin:\/usr\/local\/bin:\/usr\/bin:\/bin<\/code> and as you have guessed,
\nrunning gcc <\/code>you will get instead \/mingw64\/bin\/gcc<\/code>.<\/p>\n
This means that all three shells have the same capabilities, but because of
\nthe different orders, tools that will be picked are different. So, if you
\nwant to compile something, use the appropriate shell for what you want to
\ndo (MSYS2 program, Windows native 32 bits or Windows native 64 bits).<\/p>\n
If you are not compiling anything, then it depends. Usually, msys2_shell is
\nrecommended. However, on a bare installation, \/mingw64\/bin<\/code> is not added
\nanywhere when using msys2_shell<\/code>, problem it can causes is that if you had
\ninstalled mingw64 packages, they are not available in the shell. In my
\ncase, I have tweaked by .bash_profile<\/code> to correctly add \/mingw64\/bin<\/code>
\nafter PATH (like \/usr\/local\/bin:\/usr\/bin:\/bin:\/mingw64\/bin<\/code>). This
\nalways favor MSYS2 tools but will pick \/mingw64\/bin<\/code> when they don’t exist
\nin MSYS2 \/usr\/bin<\/code>.<\/p>\n","protected":false},"excerpt":{"rendered":"
MSYS2 introduction MSYS2 Wiki MSYS2 vs. MinGw64 MSYS vs. MinGW: internal environment variables $ uname MSYS_NT-10.0 $ uname MINGW64_NT-10.0 Package Manager $ pacman -Q <list all packages> $ pacman -Qi <package> <info about a single package> $ pacman -Ql <package> <files of a single package> Pin to Taskbar $ pacman -S msys2-launcher $ pacman -Qi […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5035","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blog.bachi.net\/index.php?rest_route=\/wp\/v2\/posts\/5035","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.bachi.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.bachi.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.bachi.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.bachi.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=5035"}],"version-history":[{"count":33,"href":"https:\/\/blog.bachi.net\/index.php?rest_route=\/wp\/v2\/posts\/5035\/revisions"}],"predecessor-version":[{"id":12176,"href":"https:\/\/blog.bachi.net\/index.php?rest_route=\/wp\/v2\/posts\/5035\/revisions\/12176"}],"wp:attachment":[{"href":"https:\/\/blog.bachi.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5035"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.bachi.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5035"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.bachi.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5035"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}