Dear all,
when trying to build a larger set of mingw-w64-packages from my own CI
system on Windows 7 using an x86_64 install of MSYS2, I currently run
into a number of difficulties, mostly around binutils, or more concretely
with nm and ld. See my corresponding issue reports here [2] [3] [4] [5].
I can not shake off the feeling that possibly its not a mingw-w64 problem,
but that my build system is at fault. So I'd like to kindly pick your
brains for insight:
- my CI system has .../msys2/usr/bin in the path, and starts bash from
there. I use "bash --login -c 'my-build-script.sh'". Is that sensible,
or does this ring any alarm signs for anyone?
- Is it recommended that I set MSYSTEM="MINGW64" and explicitly source
/etc/profile before using makepkg-mingw? I found the excellent posts
from Ray Donnely and Matthieu Vachon at [1], and my understanding is
that plain "bash --login -c" should be a good environment for
makepkg-mingw. But there are some hints that i.e. adding /mingw64 at
the end of the path might be useful in case an msys2 is missing and
the mingw64 counterpart can jump in. I did not test this yet... but
any such "black magic" is very welcome right now if you believe it
can help me out.
- I assume my CI is using the standard Windows command prompt. Is
there something that could go wrong with a bad cmd interpreter or
an incorrectly picked 32bit vs 64bit cmd or something? I guess the
fact that bash starts and does something means that the environment
should be ok? Or is there possibly some "bad karma" that I might
inherit from using a "wrong" cmd interpreter?
- The CI should start the process as my Windows GUI user. The account has
the system logon permission set, and has a password set for logon. I
chose this user because I read something about possible permission
issues when running on Windows as a pure system user account. But since
the user account is the same for GUI and CI, there should not be any
such problems, or should there?
- Is it legal to copy msys2 to a new directory and use it from there?
I used grep/perl to fixed some references to the official build repo
path C:/building/msys64, but other than that I could not find hard-
coded paths. Should the copy of msys2 work, or is a re-install required?
All the best,
Mario Emmenlauer
[1] https://sourceforge.net/p/msys2/discussion/general/thread/dcf8f4d3/
[2] https://github.com/Alexpux/MINGW-packages/issues/2186
[3] https://github.com/Alexpux/MINGW-packages/issues/2196
[4] https://github.com/Alexpux/MINGW-packages/issues/2234
[5] https://github.com/Alexpux/MINGW-packages/issues/2244
--
BioDataAnalysis GmbH, Mario Emmenlauer Tel. Buero: +49-89-74677203
Balanstr. 43 mailto: memmenlauer * biodataanalysis.de
D-81669 München http://www.biodataanalysis.de/
------------------------------------------------------------------------------
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
