On 2017/4/7 6:48, Óscar Fuentes wrote:
> The --build and --host parameters should not be needed. The configure
> script is expected to guess those values.
They are needed because otherwise I get 'x86_64-pc-msys' because at the
moment I am using devel tools from the `msys` repository to build both
packages for i686 and x86_64.
Using `--prefix=/mingw32` makes `configure` output the correct triplet
but it is also risky for overwriting system files by accident (are we
going to have `sudo` in MSYS?`. So I don't do that.
>> __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
As mentioned above I use make from the `msys` repository so it looks
like this:
E:\GitHub\mcfgthread\.build_i686_release>which make
/usr/bin/make
E:\GitHub\mcfgthread\.build_i686_release>make --version
GNU Make 4.2.1
Built for x86_64-pc-msys
Copyright (C) 1988-2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
>>> Does the build work on the classic MSYS environment?
I don't know. MSYS is merely less powerful than MSYS2 and I don't
provide support for it.
--
Best regards,
LH_Mouse
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users
