The latest version of config.guess, when run on MSYS2 64bit (posted
elsewhere on this list) with ruben's 64bit native compilers reports:
x86_64-pc-mingw32
I recall somewhere that the correct triplet should be:
x86_64-w64-mingw32
The relevant part of config.guess seems to be this:
*:MINGW64*:*)
echo ${UNAME_MACHINE}-pc-mingw64
exit ;;
*:MINGW*:*)
echo ${UNAME_MACHINE}-pc-mingw32
exit ;;
i*:MSYS*:*)
echo ${UNAME_MACHINE}-pc-msys
exit ;;
i*:windows32*:*)
# uname -m includes "-pc" on this system.
echo ${UNAME_MACHINE}-mingw32
exit ;;
I don't understand how this triplet thingy works, but would like to know
what the correct host triplet is for each of the following, and if a change
is needed in the config.guess script:
"regular" windows executables (32bit) e.g. WinXP
"regular" windows executables (64bit) e.g. Win7(x64)
Does mingw* at the end of the triplet mean "regular" windows programs? What
is msys at the end of the triplet? What is the difference between mingw32and
mingw64 at the end of the triplet?
And finally, can someone explain/point me to an explanation of how these
triplets actually work? Do they really make any difference, or are they
just used as the prefix for the compiler chosen? If I rename my compiler
and tools to "a-silly-long-prefix-gcc", "a-silly-long-prefix-g++",
"a-silly-long-prefix-ar" etc, would I have a problem compiling like this:
./configure --host=a-silly-long-prefix
make
?
--
˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
