Experimental Physics and
Industrial Control System

Ralph Lange via Core-talk <core-talk at aps.anl.gov> · Thu, 23 Apr 2020 04:38:38 -0000

But these are *not* cross-builds.

With the mingw32 tool chain, you are using a 32bit compiler executable to build 32bit artifacts.
It's the same as on Intel based Linux or Windows, where you can run the 32bit native compilers on a 64bit system.

Also, this is not a particular configuration, but the out-of-the-box
standard on MSYS2/MinGW systems. The installer creates two icons
"MinGW32 shell" and "MinGW64 shell" that start MSYS2 with the
appropriate toolchain setting.

I was assuming the EpicsHostArch script to be a user convenience
service, trying to determine the correct EPICS host architecture for the
context it is run in. The environment settings in a "MinGW32 shell" or
"MinGW64 shell" clearly indicate which toolchain is to be used. IMHO,
the EpicsHostArch script should output the setting for the intended
toolchain.

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1873406

Title:
  EpicsHostArch script does not detect recent MSYS2/MinGW setups on
  Windows

Status in EPICS Base:
  New
Status in EPICS Base 3.15 series:
  New
Status in EPICS Base 7.0 series:
  New

Bug description:
  On MSYS2/MinGW installations, the EpicsHostArch script does not
  recognize the host platform correctly.

  64bit:
  $ ./startup/EpicsHostArch
  lib/perl/EpicsHostArch.pl: Architecture 'x86_64-msys-thread-multi' not recognized

  32bit:
  $ ./startup/EpicsHostArch
  lib/perl/EpicsHostArch.pl: Architecture 'x86_64-msys-thread-multi' not recognized

  Which is not surprising, as the underlying MSYS2 subsystem is the
  same, and the difference is in the environment settings that point to
  the appropriate toolchain.

  64bit:
  $ echo $PATH
  /mingw64/bin:/usr/local/bin:/usr/bin:/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
  $ printenv | grep MSYSTEM
  MSYSTEM_CARCH=x86_64
  MSYSTEM_CHOST=x86_64-w64-mingw32
  MSYSTEM_PREFIX=/mingw64
  MSYSTEM=MINGW64

  32bit:
  $ echo $PATH
  /mingw32/bin:/usr/local/bin:/usr/bin:/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
  $ printenv | grep MSYSTEM
  MSYSTEM_CARCH=i686
  MSYSTEM_CHOST=i686-w64-mingw32
  MSYSTEM_PREFIX=/mingw32
  MSYSTEM=MINGW32

  NB: I am impressed by the clarity and simplicity of MSYS2 / MinGW

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1873406/+subscriptions

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System