--- Comment #8 from nightstrike at gmail dot com 2010-04-01 11:54 ---
I'd recommend closing this as invalid. We build 12 relocatable toolchains for
windows daily for http://mingw-w64.sf.net/
I'm pretty sure it works :)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42886
--- Comment #9 from aflyhorse at foxmail dot com 2010-04-01 13:48 ---
(In reply to comment #8)
I'd recommend closing this as invalid. We build 12 relocatable toolchains for
windows daily for http://mingw-w64.sf.net/
I'm pretty sure it works :)
Agree. I've made a bootstrap a
--- Comment #10 from aflyhorse at foxmail dot com 2010-04-01 13:58 ---
night-strike can i ask a question that had x86_64-w64-mingw32 supported libgcj
yet? I failed even explictly --enable-libgcj... and a so-called wiki of
mingw-w64 (http://www.cadforte.com/wiki/index.php/Java) said Java
--- Comment #11 from rguenth at gcc dot gnu dot org 2010-04-01 14:18
---
Invalid then.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #12 from nightstrike at gmail dot com 2010-04-01 15:27 ---
(In reply to comment #10)
night-strike can i ask a question that had x86_64-w64-mingw32 supported libgcj
yet? I failed even explictly --enable-libgcj... and a so-called wiki of
mingw-w64
--- Comment #7 from rguenth at gcc dot gnu dot org 2010-03-31 11:52 ---
Back to P3 due to waiting state.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from andriys at gmail dot com 2010-03-21 08:15 ---
(In reply to comment #1)
This is probably due to the way you built GCC. To have a completely
relocatable toolchain, you need to use the --with-sysroot option to configure,
I've just checked out the latest sources from
--- Comment #4 from nightstrike at gmail dot com 2010-03-21 14:56 ---
(In reply to comment #3)
(In reply to comment #1)
This is probably due to the way you built GCC. To have a completely
relocatable toolchain, you need to use the --with-sysroot option to
configure,
I've just
--- Comment #5 from d dot g dot gorbachev at gmail dot com 2010-03-21
18:00 ---
My GCC (4.4 and 4.5) were configured with the following options:
`--build=mingw32 --enable-languages=c,c++
--enable-version-specific-runtime-libs --disable-win32-registry --disable-nls
--disable-shared'. I
--- Comment #6 from aflyhorse at foxmail dot com 2010-03-22 01:00 ---
In my recent build
I configured the binutils as:
../src/configure --target=x86_64-w64-mingw32
--enable-targets=x86_64-w64-mingw32,i686-w64-mingw32 --disable-shared
--enable-static --disable-nls --with-mpc=/local
--- Comment #2 from steven at gcc dot gnu dot org 2010-03-20 13:02 ---
Waiting for OP to try suggestion of comment #1.
--
steven at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #1 from nightstrike at gmail dot com 2010-03-19 14:25 ---
This is probably due to the way you built GCC. To have a completely
relocatable toolchain, you need to use the --with-sysroot option to configure,
and you need to set it equal to prefix or below prefix in the
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42886
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.5.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42886
14 matches
Mail list logo
