* [Bug libstdc++/56332] libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination
2013-02-14 22:30 [Bug libstdc++/56332] New: libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination devurandom at gmx dot net
@ 2013-02-14 22:30 ` devurandom at gmx dot net
2013-02-15 8:39 ` mikpe at it dot uu.se
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: devurandom at gmx dot net @ 2013-02-14 22:30 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56332
--- Comment #1 from devurandom at gmx dot net 2013-02-14 22:30:16 UTC ---
Created attachment 29459
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29459
gcc-4.7.2-libstdc++-v3-os_include_dir-and-error_constants_dir-for-mingw64.patch
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug libstdc++/56332] libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination
2013-02-14 22:30 [Bug libstdc++/56332] New: libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination devurandom at gmx dot net
2013-02-14 22:30 ` [Bug libstdc++/56332] " devurandom at gmx dot net
@ 2013-02-15 8:39 ` mikpe at it dot uu.se
2013-02-15 10:38 ` devurandom at gmx dot net
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: mikpe at it dot uu.se @ 2013-02-15 8:39 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56332
--- Comment #2 from Mikael Pettersson <mikpe at it dot uu.se> 2013-02-15 08:39:20 UTC ---
For mingw-w64 isn't the triplet supposed to be 'x86_64-w64-mingw32'? Or has
the 'old mingw' now grown its own 64-bit support?
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug libstdc++/56332] libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination
2013-02-14 22:30 [Bug libstdc++/56332] New: libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination devurandom at gmx dot net
2013-02-14 22:30 ` [Bug libstdc++/56332] " devurandom at gmx dot net
2013-02-15 8:39 ` mikpe at it dot uu.se
@ 2013-02-15 10:38 ` devurandom at gmx dot net
2013-02-15 14:10 ` mikpe at it dot uu.se
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: devurandom at gmx dot net @ 2013-02-15 10:38 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56332
--- Comment #3 from devurandom at gmx dot net 2013-02-15 10:37:58 UTC ---
(In reply to comment #2)
> For mingw-w64 isn't the triplet supposed to be 'x86_64-w64-mingw32'? Or has
> the 'old mingw' now grown its own 64-bit support?
That would be quite confusing, because the 32-bit target seems to be named
i386-pc-mingw32 and not i386-w32-mingw32. IMO w64-mingw32 also looks
ridiculous, but that is just my opinion. And also the package is named
mingw64-runtime in Gentoo. On the other hand the project itself seems to be
named mingw-w64 - which just makes w64-mingw32 look more wrong.
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug libstdc++/56332] libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination
2013-02-14 22:30 [Bug libstdc++/56332] New: libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination devurandom at gmx dot net
` (2 preceding siblings ...)
2013-02-15 10:38 ` devurandom at gmx dot net
@ 2013-02-15 14:10 ` mikpe at it dot uu.se
2013-02-16 3:01 ` pinskia at gcc dot gnu.org
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: mikpe at it dot uu.se @ 2013-02-15 14:10 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56332
--- Comment #4 from Mikael Pettersson <mikpe at it dot uu.se> 2013-02-15 14:09:35 UTC ---
Confusing or not, the triplet is as I stated, see e.g.:
http://sourceforge.net/apps/trac/mingw-w64/wiki/Answer%20Multilib%20Toolchain
And the 32-bit target is 'i686-w64-mingw32' for mingw-w64's 32-bit mode,
'i386-pc-mingw32' is "old mingw" which is an entirely different entity.
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug libstdc++/56332] libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination
2013-02-14 22:30 [Bug libstdc++/56332] New: libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination devurandom at gmx dot net
` (3 preceding siblings ...)
2013-02-15 14:10 ` mikpe at it dot uu.se
@ 2013-02-16 3:01 ` pinskia at gcc dot gnu.org
2013-02-16 13:15 ` devurandom at gmx dot net
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: pinskia at gcc dot gnu.org @ 2013-02-16 3:01 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56332
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-02-16 03:00:45 UTC ---
(In reply to comment #2)
> For mingw-w64 isn't the triplet supposed to be 'x86_64-w64-mingw32'?
The other point is that the Windows API are still called win32 on x64 Windows;
that is the w32 part.
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug libstdc++/56332] libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination
2013-02-14 22:30 [Bug libstdc++/56332] New: libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination devurandom at gmx dot net
` (4 preceding siblings ...)
2013-02-16 3:01 ` pinskia at gcc dot gnu.org
@ 2013-02-16 13:15 ` devurandom at gmx dot net
2013-02-16 13:21 ` devurandom at gmx dot net
2013-05-13 20:00 ` ktietz at gcc dot gnu.org
7 siblings, 0 replies; 9+ messages in thread
From: devurandom at gmx dot net @ 2013-02-16 13:15 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56332
--- Comment #6 from devurandom at gmx dot net 2013-02-16 13:15:27 UTC ---
Ok...
I assumed that in the cpu-vendor-os triplet the os part contains the reference
to the c library and/or kernel, while vendor refers to the distribution that
packaged the compiler (or is often just "pc" for i386). Apparently this was
completely wrong.
I'll ask the Gentoo maintainers to rename the package to something that is not
plain wrong.
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug libstdc++/56332] libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination
2013-02-14 22:30 [Bug libstdc++/56332] New: libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination devurandom at gmx dot net
` (5 preceding siblings ...)
2013-02-16 13:15 ` devurandom at gmx dot net
@ 2013-02-16 13:21 ` devurandom at gmx dot net
2013-05-13 20:00 ` ktietz at gcc dot gnu.org
7 siblings, 0 replies; 9+ messages in thread
From: devurandom at gmx dot net @ 2013-02-16 13:21 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56332
--- Comment #7 from devurandom at gmx dot net 2013-02-16 13:20:49 UTC ---
P.S: Is relaxing the match to accept "mingw*", because the library and compiler
are called mingw(-w64), an option? That shouldn't hurt anyone and not make
anything more complicated either.
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug libstdc++/56332] libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination
2013-02-14 22:30 [Bug libstdc++/56332] New: libstdc++-v3 does not support x86_64-pc-mingw64: No support for this host/target combination devurandom at gmx dot net
` (6 preceding siblings ...)
2013-02-16 13:21 ` devurandom at gmx dot net
@ 2013-05-13 20:00 ` ktietz at gcc dot gnu.org
7 siblings, 0 replies; 9+ messages in thread
From: ktietz at gcc dot gnu.org @ 2013-05-13 20:00 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56332
Kai Tietz <ktietz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |ktietz at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #8 from Kai Tietz <ktietz at gcc dot gnu.org> ---
There is no such triplet x86_64-pc-mingw64 support.
^ permalink raw reply [flat|nested] 9+ messages in thread