Issue With Autoreconf (MSYS2)
I'm trying to execute a build under MSYS2, and autoreconf doesn't seem to work. The console log is here.
From the log, it looks like one of the perl modules associated with the autoconf package is missing. I did try executing the same on a local windows virtual machine and it doesn't seem to have any issue.
Can anybody help me with this?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Ray Donnelly on 25 Oct, 2015 02:07 PM
You are giving (a very old) Git for Windows (it was called msysGit in those days and it used MSYS) priority over MSYS2 in your PATH, so the sh.exe that is run isn't MSYS2's bash, but instead a really old one from MSYS.
Change:
set PATH=%PATH%;C:\msys64\usr\bin
To:
set PATH=C:\msys64\usr\bin;%PATH%
Also you should take care to set the MSYSTEM env. variable to one of MINGW32, MINGW64 or MSYS before running sh (and you should be explicit about wanting to use a good shell such as bash instead).
If you can address questions regarding MSYS2 to the MSYS2 project itself I'd appreciate it as AppVeyor probably can do without the hassles of supporting MSYS2 while we're more than happy to do that. Having said that, they may want to build up a knowledge base of solutions here, @ Feodor Fitsner, I'd appreciate some guidance on this matter actually!
2 Posted by jason on 25 Oct, 2015 07:42 PM
Thanks Ray, I appreciate the help. I appreciate the extra information too. I only recently switched from cygwin to msys2, but so far I'm extremely happy with it. It's been especially awesome for building anything that needs POSIX.
That solved the problem with autoreconf, but there still seems to be an issue running a configure script. I'm not sure if it's an issue with appveyor or msys2 though. I did try executing under bash, but unfortunately to no avail.
It would be nice if there were a bit more information on getting builds running under msys2. I definitely don't want to take up any more time than necessary for the appveyor team. I haven't been able to find much appveyor specific documentation for msys2. One of the other questions I have is on setting up pip for python, but I want to get the build working before starting on that.
3 Posted by jason on 31 Oct, 2015 06:12 AM
If anyone else has the same problem, I was able to resolve the final issues with my build including installing python (pacman), pip, and cram for functional testing. I'm not sure if pacman packages are cached or should be cached.
To resolve the issue with the configure script, I had to add a simple workaround.
Support Staff 4 Posted by Feodor Fitsner on 31 Oct, 2015 11:56 PM
Looks great! Thanks for sharing the solution with the rest of the community!
5 Posted by jason on 03 Nov, 2015 06:09 AM
No problem @Feodor Fitsner. I appreciate the MSYS2 setup.
Also I'm wondering, should I cache the pacman packages necessary for the build? Build speed isn't a concern for this (simple codebase), but the downloads might use a little bandwidth (12MiB/build for MSYS2 Python).
Support Staff 6 Posted by Feodor Fitsner on 03 Nov, 2015 07:24 AM
I don't think cache would give any performance gain here and it's OK to download it every build.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:01 AM.