At Thu, 3 Apr 2003 17:30:32 -0500,
Clint Adams wrote:
> > issue. If gcc 3.3 will be back to -m64 aware, we re-enable these
> > configurations. Do you know the status of gcc-3.3 which is ready for
> > -m64?
>
> gcc-3.3 3.3-0pre3, currently in sid, builds -m64 binaries that work.
Excellent. OK,
Your message dated Fri, 4 Apr 2003 00:37:49 +0200
with message-id <[EMAIL PROTECTED]>
and subject line gcc build failures fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibi
LAST_UPDATED: Mon Mar 31 21:22:25 UTC 2003
Native configuration is m68k-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.eh/spec3.C Execution test
FAIL: g++.eh/spec4.C Execution test
XPASS: g++.other/init5.C Execution test
=== g++ Summary ===
LAST_UPDATED: Mon Mar 31 21:17:54 UTC 2003
Native configuration is sparc-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/compat/break/bitfield7 y_tst.o compile
UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o link
UNRESOLVED: g++.dg/compat/break/bi
LAST_UPDATED: Mon Mar 31 21:22:25 UTC 2003
Native configuration is mips-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/debug/debug4.C (test for excess errors)
FAIL: g++.dg/debug/debug4.C (test for excess errors)
FAIL: g++.dg/debug/debug4.C (test for excess
LAST_UPDATED: Mon Mar 31 21:22:25 UTC 2003
Native configuration is hppa-unknown-linux-gnu
=== g++ tests ===
Running target unix
XPASS: g++.mike/eh33.C (test for excess errors)
XPASS: g++.mike/eh33.C Execution test
XPASS: g++.mike/eh50.C (test for excess errors)
XPASS: g++.mike/
> issue. If gcc 3.3 will be back to -m64 aware, we re-enable these
> configurations. Do you know the status of gcc-3.3 which is ready for
> -m64?
gcc-3.3 3.3-0pre3, currently in sid, builds -m64 binaries that work.
7 matches
Mail list logo