Processing commands for [EMAIL PROTECTED]:
> tag 471831 + wontfix
Bug#471831: g++-3.4 fails to link
There were no tags set.
Tags added: wontfix
> tag 441104 + wontfix
Bug#441104: g77-3.4: Code linked to libg2c segfaults on f_open(), g_char()
Tags were: wontfix
Tags added: wontfix
> tag 452115 +
Processing commands for [EMAIL PROTECTED]:
> tag 407417 + wontfix
Bug#407417: Confusing versioning of libstdc++6[-...]
Tags were: wontfix
Tags added: wontfix
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Deb
Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #323285,
regarding libg2c0-dev: includes 32-bit compatibility libraries in pure 64-bit
amd64 installation
to be m
Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #425053,
regarding Suggests: g77-3.4-doc -- but no such package exists
to be marked as done.
This means that you
Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #452115,
regarding gcc-4.2: Incorrect results with abs()
to be marked as done.
This means that you claim that the
Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #323285,
regarding libg2c0-dev: Dangling symlink /usr/lib64/libg2c.so
to be marked as done.
This means that you c
Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #323285,
regarding /usr/lib64 should be in a separate package
to be marked as done.
This means that you claim tha
Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #471831,
regarding g++-3.4 fails to link
to be marked as done.
This means that you claim that the problem has bee
Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #441104,
regarding g77-3.4: Code linked to libg2c segfaults on f_open(), g_char()
to be marked as done.
This mean
Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #420533,
regarding utterly empty man page
to be marked as done.
This means that you claim that the problem has be
Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #437537,
regarding Dangling symlink /usr/share/man/man1/i486-linux-gnu-g77-3.4.1
to be marked as done.
This means
Your message dated Sat, 25 Oct 2008 02:51:10 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Confusing versioning of libstdc++6[-...]
has caused the Debian Bug report #407417,
regarding Confusing versioning of libstdc++6[-...]
to be marked as done.
This means that you claim that th
Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #299188,
regarding gcc: -ffreestanding and builtins don't work as expected
to be marked as done.
This means that
Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #399100,
regarding gcc-3.4: Library libgccl does not build
to be marked as done.
This means that you claim that t
Your message dated Sat, 25 Oct 2008 02:27:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#485878: g++-3.4 no longer in testing
has caused the Debian Bug report #485878,
regarding g++-3.4 no longer in testing
to be marked as done.
This means that you claim that the problem ha
Processing commands for [EMAIL PROTECTED]:
> tag 485878 + wontfix
Bug#485878: g++-3.4 no longer in testing
There were no tags set.
Tags added: wontfix
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bug
LAST_UPDATED: Thu Oct 23 19:32:02 UTC 2008 (revision 141326)
Target: sparc-linux-gnu
gcc version 4.4.0 20081023 (experimental) [trunk revision 141326] (Debian
20081023-1)
=== acats tests ===
FAIL: c410001
FAIL: c41328a
FAIL: cb20001
FAIL: cb4004a
FAIL: cb41003
FAIL:
LAST_UPDATED: Thu Oct 23 19:32:02 UTC 2008 (revision 141326)
Target: powerpc-linux-gnu
gcc version 4.4.0 20081023 (experimental) [trunk revision 141326] (Debian
20081023-1)
Native configuration is powerpc-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/ext
LAST_UPDATED: Thu Oct 23 19:32:02 UTC 2008 (revision 141326)
Target: i486-linux-gnu
gcc version 4.4.0 20081023 (experimental) [trunk revision 141326] (Debian
20081023-1)
=== acats tests ===
=== acats Summary ===
# of expected passes2315
# of unexpect
LAST_UPDATED: Thu Oct 23 13:50:22 UTC 2008 (revision 141322)
Target: sparc-linux-gnu
gcc version 4.3.2 (Debian 4.3.2-2~exp2)
Native configuration is sparc-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/opt/anchor1.C execution test
=== g++
LAST_UPDATED: Thu Oct 23 13:50:22 UTC 2008 (revision 141322)
Target: powerpc-linux-gnu
gcc version 4.3.2 (Debian 4.3.2-2~exp2)
Native configuration is powerpc-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/ext/altivec-3.C execution test
FAIL: g++.dg/ext/ve
LAST_UPDATED: Thu Oct 23 13:50:22 UTC 2008 (revision 141322)
Target: i486-linux-gnu
gcc version 4.3.2 (Debian 4.3.2-2~exp2)
Native configuration is i486-pc-linux-gnu
=== g++ tests ===
Running target unix
=== g++ Summary for unix ===
# of expected passes
LAST_UPDATED: Thu Oct 23 13:50:22 UTC 2008 (revision 141322)
Target: x86_64-linux-gnu
gcc version 4.3.2 (Debian 4.3.2-2~exp2)
Native configuration is x86_64-pc-linux-gnu
=== g++ tests ===
Running target unix
=== g++ Summary for unix ===
# of expected passes
--- Comment #16 from pinskia at gcc dot gnu dot org 2008-10-24 21:36
---
Verified fixes the PPC GNU/Linux libstdc++ failures that I was receiving too.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37815
--- You are receiving this mail because: ---
You are on the CC list f
--- Comment #15 from jsm28 at gcc dot gnu dot org 2008-10-24 19:36 ---
Subject: Bug 456
Author: jsm28
Date: Fri Oct 24 19:34:52 2008
New Revision: 141349
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=141349
Log:
PR c/456
PR c/5675
PR c/19976
PR c
Accepted:
cpp-4.3_4.3.2-2~exp2_amd64.deb
to pool/main/g/gcc-4.3/cpp-4.3_4.3.2-2~exp2_amd64.deb
cpp-4.3_4.3.2-2~exp2_i386.deb
to pool/main/g/gcc-4.3/cpp-4.3_4.3.2-2~exp2_i386.deb
cpp-4.3_4.3.2-2~exp2_powerpc.deb
to pool/main/g/gcc-4.3/cpp-4.3_4.3.2-2~exp2_powerpc.deb
cpp-4.3_4.3.2-2~exp2_spar
Accepted:
gcc-snapshot_20081023-1.diff.gz
to pool/main/g/gcc-snapshot/gcc-snapshot_20081023-1.diff.gz
gcc-snapshot_20081023-1.dsc
to pool/main/g/gcc-snapshot/gcc-snapshot_20081023-1.dsc
gcc-snapshot_20081023-1_i386.deb
to pool/main/g/gcc-snapshot/gcc-snapshot_20081023-1_i386.deb
gcc-snapshot
gcc-snapshot_20081023-1_multi.changes uploaded successfully to localhost
along with the files:
gcc-snapshot_20081023-1.dsc
gcc-snapshot_20081023.orig.tar.gz
gcc-snapshot_20081023-1_powerpc.deb
gcc-snapshot_20081023-1_sparc.deb
gcc-snapshot_20081023-1.diff.gz
gcc-snapshot_20081023-1_i386
gcc-4.3_4.3.2-2~exp2_multi.changes uploaded successfully to localhost
along with the files:
lib64gcc1-dbg_4.3.2-2~exp2_i386.deb
libobjc2_4.3.2-2~exp2_sparc.deb
libstdc++6-4.3-dbg_4.3.2-2~exp2_i386.deb
libgomp1_4.3.2-2~exp2_i386.deb
lib64gfortran3-dbg_4.3.2-2~exp2_sparc.deb
gcc-4.3-multi
Hi,
Bastian Blank wrote:
It's obviously buggy to emit a warning on standards-mandated behaviour!
I know you can turn this warning off with -Wno-unknown-pragmas, but
that's not something you want to be doing in production code.
Please show the part of the standard. A compiler may produce warni
30 matches
Mail list logo
