No, the MSYS2 MinGW make packages do not supply a "make.exe". That would
cause lots of compatibility problems and break a lot of packages because of
the bugs and quirks in MinGW make.
$ pacman -Ql mingw-w64-i686-make
mingw-w64-i686-make /mingw32/
mingw-w64-i686-make /mingw32/bin/
mingw-w64-i686-make /mingw32/bin/mingw32-make.exe
mingw-w64-i686-make /mingw32/include/
mingw-w64-i686-make /mingw32/include/gnumake.h
mingw-w64-i686-make /mingw32/lib/
You might modify the Makefile to convert the path using the cygpath
utility, doing something like:
echo "#include \"$(shell cygpath -w $<)\"" > $@
LH_Mouse will probably have a better suggestion, and it looks like you
already asked him on GitHub: https://github.com/lhmouse/mcfgthread/issues/25
--David Grayson
On Thu, Apr 6, 2017 at 3:48 PM, Óscar Fuentes <o...@wanadoo.es> wrote:
> Edward Diener <eldlistmaili...@tropicsoft.com>
> writes:
>
> >> Please show the exact steps for replicating the problem, including the
> >> method you use to start the MSYS2 shell.
> >
> > I start the shell by double-clicking the program item "MSYS2 MinGW
> 64-bit".
>
> Good.
>
> > The library I am trying to build is mfcgthread from
> > https://github.com/lhmouse/mcfgthread. I am using a slightly modified
> > build script. The pertinent lines are:
> >
> > autoreconf -i
> > CPPFLAGS='-DNDEBUG'
> > CFLAGS='-O3 -ffunction-sections -fdata-sections -m64'
> > LDFLAGS='-Wl,-s,--gc-sections'
> > configure --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32
>
> The --build and --host parameters should not be needed. The configure
> script is expected to guess those values.
>
> > make -j4
> > make install
> >
> >>
> >> On the shell you use for the build, if you type the command
> >>
> >> which gcc.exe
> >>
> >> what's the output?
> >
> > /mingw64/bin/gcc.exe
> >
> >>
> >> Configure scripts are usually made of standardized, off-the-shelf
> >> components and should detect that you are using the MinGW-w64 toolset
> >> and behave in accordance, but the part that puts absolute file paths on
> >> the generated __pch.h header possibly is project-specific and might be
> >> problematic unless it was written with portability in mind.
> >
> > I will notify the mfcgthread of this. The relevant part of Makefile.am
> is:
> >
> > __pch.h: ${srcdir}/src/env/_crtdef.h
> > echo "#include \"$<\"" > $@
>
> I guess you are using the MSYS2-dependent make.exe executable. Please
> try using the make.exe executable for MinGW-w64 instead:
>
> $ pacman -S mingw-w64-x86_64-make
>
> Now
>
> $ which make.exe
>
> should output
>
> /mingw64/bin/make.exe
>
>
>
> >> Does the build work on the classic MSYS environment?
> >
> > I never tried it.
> >
> >> Are there reports
> >> of it working on Windows at all?
> >
> > See https://github.com/lhmouse/mcfgthread/blob/master/README.md.
>
> lhmouse is an active member of the MinGW-w64 project (now he is posting
> on the mailing list as Liu Hao). I see that you already posted there and
> opened an issue on Github.
>
>
> ------------------------------------------------------------
> ------------------
> 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
>
------------------------------------------------------------------------------
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
