[Bug target/38294] Enable multilib support for mingw

2009-08-31 Thread ktietz at gcc dot gnu dot org
--- Comment #12 from ktietz at gcc dot gnu dot org 2009-08-31 19:49 --- (In reply to comment #11) Created an attachment (id=17259) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17259action=view) [edit] Kai's attempt This patch has a few caveats: You can't use the winsup

[Bug target/38294] Enable multilib support for mingw

2009-08-31 Thread ktietz at gcc dot gnu dot org
--- Comment #13 from ktietz at gcc dot gnu dot org 2009-08-31 19:52 --- As the change is already applied to head, I close this. -- ktietz at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/38294] Enable multilib support for mingw

2009-02-05 Thread nightstrike at gmail dot com
--- Comment #11 from nightstrike at gmail dot com 2009-02-06 04:21 --- Created an attachment (id=17259) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17259action=view) Kai's attempt This patch has a few caveats: You can't use the winsup link hack to work around the issue that

[Bug target/38294] Enable multilib support for mingw

2008-12-13 Thread nightstrike at gmail dot com
--- Comment #4 from nightstrike at gmail dot com 2008-12-13 21:19 --- As per jakub, it is space separated. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294

[Bug target/38294] Enable multilib support for mingw

2008-12-13 Thread ktietz at gcc dot gnu dot org
--- Comment #5 from ktietz at gcc dot gnu dot org 2008-12-13 21:46 --- Reasoned by the fact, that this patch will solve our build failures for w64, it is really more to be treated as regression. NightStrike, when all tests you are doing at the moment are passing, I'll sent it tomorrow

[Bug target/38294] Enable multilib support for mingw

2008-12-13 Thread nightstrike at gmail dot com
--- Comment #6 from nightstrike at gmail dot com 2008-12-13 21:59 --- Created an attachment (id=16906) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16906action=view) Third attempt There were a few lines in t-mingw32 that were commented out and shouldn't have been there. Fixed in

[Bug target/38294] Enable multilib support for mingw

2008-12-13 Thread nightstrike at gmail dot com
--- Comment #7 from nightstrike at gmail dot com 2008-12-13 23:01 --- Tested and verified on win64 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294

[Bug target/38294] Enable multilib support for mingw

2008-12-13 Thread nightstrike at gmail dot com
--- Comment #8 from nightstrike at gmail dot com 2008-12-14 00:11 --- To complete this patch, we need to make multilib not be the default. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294

[Bug target/38294] Enable multilib support for mingw

2008-12-13 Thread dannysmith at users dot sourceforge dot net
--- Comment #9 from dannysmith at users dot sourceforge dot net 2008-12-14 05:54 --- (In reply to comment #5) Reasoned by the fact, that this patch will solve our build failures for w64, it is really more to be treated as regression. NightStrike, when all tests you are doing at

[Bug target/38294] Enable multilib support for mingw

2008-12-13 Thread ktietz at gcc dot gnu dot org
--- Comment #10 from ktietz at gcc dot gnu dot org 2008-12-14 07:50 --- (In reply to comment #9) (In reply to comment #5) Reasoned by the fact, that this patch will solve our build failures for w64, it is really more to be treated as regression. NightStrike, when all tests

[Bug target/38294] Enable multilib support for mingw

2008-12-08 Thread ktietz at gcc dot gnu dot org
--- Comment #3 from ktietz at gcc dot gnu dot org 2008-12-08 20:16 --- From my point of view this patch seems to be ok. Multilib is just enabled for 64-bit default target, what makes sende at the moment. Just about the point of multilib library specifier, I am not sure. Shouldn't it

[Bug target/38294] Enable multilib support for mingw

2008-12-07 Thread nightstrike at gmail dot com
--- Comment #2 from nightstrike at gmail dot com 2008-12-08 07:48 --- Created an attachment (id=16849) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16849action=view) Second attempt This gets us further along -- nightstrike at gmail dot com changed: What