On 07/11/13 11:51 AM, Salter, Thomas A wrote:
Is MinGW/MSYS supposed to be supported now? Is a particular version required?
The only version I could find was this: $ /usr/bin/msysinfo | head reports:
msysinfo-1.3: Send this to the MSYS support list: MSYS 1.0.17(0.48/3/2) 2011-04-24 23:39 i686 unknown; targ=MINGW32 GNU bash, version 3.1.17(1)-release (i686-pc-msys); ENV=.profile GNU Make 3.81This program built for i686-pc-msys; MAKE_MODE=unix
That was about 12 months ago. I admit I stopped looking after that. Looks like uname matches what you posted below: $ uname -r 1.0.17(0.48/3/2) $ uname -m i686 $ uname -r 1.0.17(0.48/3/2) $ uname -s MINGW32_NT-6.1 $ uname -v 2011-04-24 23:39
I've gotten builds to work with cygwin and wanted to try MinGW/MSYS. It ails almost immediately because it can't find cpio. It acts as though the uname result isn't recognized.
MSYS was working for OpenJDK8 builds. I could not find cpio for MinGW/MSYS, so I implemented a workaround using back-to-back tar. That could have bitrotted, so I'll have to do a test build to verify.
I'm running on a 64-bit Windows 7 system. The complete config.log is attached, but the part that I think matters is here: hostname = USTR-SALTERTA-1 uname -m = i686 uname -r = 1.0.17(0.48/3/2) uname -s = MINGW32_NT-6.1 uname -v = 2011-04-24 23:39 ... configure:4413: found /usr/bin/cp configure:4425: result: /usr/bin/cp configure:4454: checking for cpio configure:4487: result: no configure:4502: Could not find cpio! configure:4504: error: Cannot continue
If using MSYS, we shouldn't require cpio in the sanity check. I'll try a test fix later today and send a patch if it works.
Tim
