On 2017-06-17 01:23-0700 Alan W. Irwin wrote:

So it is obviously time for me to transcribe and reorganize these
results as an official wine-staging bug report.

See <https://bugs.winehq.org/show_bug.cgi?id=43193>.  I would
appreciate it if those who can confirm this bug (like Norbert) add
their reports at that location since I imagine the more such
confirmations, the more likely the wine-staging developers will fix
this bug in a timely manner.

By the way, my motivation for attempting to install MSYS2 on the
wine-staging platform is I would like to build and test PLplot, the
timeephem projects ephcom and te_gen, and FreeEOS on that platform. My
prior experience with attempting to do the same thing on MinGW/MSYS
(several years ago when that platform was fairly reliable) was quite
successful although extremely slow because of the huge (typically 0.5
seconds) startup latency of executables being launched on MinGW/MSYS
(and presumably MinGW-w64/MSYS2 also).

My mental model of why that latency is so large (corresponding to
something like 100 million operations) is MinGW-w64/MSYS2 forking to
start applications is already quite complex (just as is also the case
for Cygwin).  And each of those many Windows commands is translated by
Wine-staging (or Wine) into many Linux commands.  So fundamentally
10000 ops * 10000 ops = 100 million ops to start up an application,
and there is no way around this latency issue.

That startup latency doesn't hurt gamers much since it only happens
when they start a game.  That latency becomes a serious issue,
however, when building and testing software since most build systems
implement those tasks as a large number of interdependent small
applications that are run (each of which has that 0.5 second penalty
applied).

Despite the expected slowness due to startup latency, running MSYS2 on
wine-staging should be quite valuable to me since it allows me to
avoid paying a tax to a convicted monopolist that I dislike.  However,
despite my personal distaste for Microsoft's attempts to extend its PC
monopoly, I do recognize many developers like to use Windows to
develop their own free software, and I don't mind at all giving them a
hand to do that because I feel free software is important regardless
of what operating system is running.  Thus, once the above
wine-staging bug is fixed, and assuming the rest of MSYS2 works OK on
that platform as before, that should allow me to easily collaborate
with my software development colleagues that have access to MSYS2 on
the Microsoft version of the Windows platform.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Msys2-users mailing list
Msys2-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/msys2-users

Reply via email to