Processing commands for [EMAIL PROTECTED]:
> tag 189466 + fixed
Bug#189466: Fully qualified name with arch desirable
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debi
Accepted:
cpp-3.2-doc_3.2.3-4_all.deb
to pool/main/g/gcc-3.2/cpp-3.2-doc_3.2.3-4_all.deb
cpp-3.2_3.2.3-4_sparc.deb
to pool/main/g/gcc-3.2/cpp-3.2_3.2.3-4_sparc.deb
g++-3.2_3.2.3-4_sparc.deb
to pool/main/g/gcc-3.2/g++-3.2_3.2.3-4_sparc.deb
g77-3.2-doc_3.2.3-4_all.deb
to pool/main/g/gcc-3.2/
There are disparities between your recently accepted upload and the
override file for the following file(s):
gcc-3.2-base_3.2.3-4_sparc.deb: package says priority is important, override
says optional.
Either the package or the override file is incorrect. If you think
the override is correct and
tag 189466 + fixed
quit
This message was generated automatically in response to a
non-maintainer upload. The .changes file follows.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 2 Jun 2003 23:43:04 +0200
Source: gcc-3.2
Binary: gcc-3.2-base libstdc++5-dev cpp-3.2-doc li
3.3 branch and mainline (20030604). Took me a while, because
this is not
reproducible with mipsel-elf target. Hopefully the reduced testcase I've
attached will help track
this one down...
Dara
--- You are receiving this mail because: ---
You reported the bug, or are watchin
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11084
--- Additional Comments From [EMAIL PROTECTED] 2003-06-05 00:20 ---
Created an attachment (id=4171)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=4171&action=view)
re
LAST_UPDATED:
Native configuration is s390-ibm-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/eh/forced1.C execution test
FAIL: g++.dg/tls/init-2.C (test for excess errors)
FAIL: g++.eh/terminate2.C Execution test
XPASS: g++.other/init5.C Execution test
LAST_UPDATED:
Native configuration is i386-pc-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/tls/init-2.C (test for excess errors)
XPASS: g++.other/init5.C Execution test
=== g++ Summary ===
# of expected passes7997
# of unexpected fa
LAST_UPDATED:
Native configuration is alpha-unknown-linux-gnu
=== libjava tests ===
Running target unix
FAIL: initexc execution - gij test
FAIL: initexc execution - gij test
=== libjava Summary ===
# of expected passes2987
# of unexpected failures
LAST_UPDATED:
Native configuration is hppa-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/compat/break/bitfield7 x_tst.o compile
UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o link
UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o execut
> On Mon, Jun 02, 2003 at 05:10:38PM -0400, John David Anglin wrote:
> > tmpdir/sh1p.o(.text+0x0): In function `shlib_mainvar':
> > /home/dave/binutils-2.14.90/src/ld/testsuite/ld-elfvsb/sh1.c:32: undefined
> > refer
> > ence to `mainvar'
> > ...
> > FAIL: visibility (hidden)
>
> Fixing this one
Accepted:
chill_2.95.4-22_sparc.deb
to pool/main/g/gcc-defaults/chill_2.95.4-22_sparc.deb
cpp_3.2-6_sparc.deb
to pool/main/g/gcc-defaults/cpp_3.2-6_sparc.deb
g++_3.2-6_sparc.deb
to pool/main/g/gcc-defaults/g++_3.2-6_sparc.deb
g77_3.2-6_sparc.deb
to pool/main/g/gcc-defaults/g77_3.2-6_sparc.
Package: gcc-3.3
Version: 1:3.3-2
Severity: important
Tags: upstream
This is a regression from GCC 3.2.
While compiling XFree86 for mips and mipsel, each build fails
identically.
http://buildd.debian.org/fetch.php?&pkg=xfree86&ver=4.2.1-7&arch=mipsel&stamp=1054296758&file=log&as=raw
http://build
Package: gcc-3.3
Version: 1:3.3-2
Severity: important
Tags: upstream, moreinfo
You're going to need more information from me on this, I'm sure, but I'm
filing the bug now so I don't forget to file it at all.
When testing XFree86 4.2.1-7 on my PowerPC I found that compiling the
tree with -O2 (per
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9209
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|---
The bug tracking, bug forwarding is getting too time consuming ...
I'd like to ask for kind of teamwork on this topic (separated by
architecture, language, etc ...).
When replying to "wrong" bug reports, it would be nice to respond to
###-done, insted to ###, so the report gets closed and doesn't
I'm away ... for that reason, I didn't update 3.3 to the current CVS.
My current build files are checked in.
Matthias
Package: gcc-3.3
Version: 3.3-2
Severity: important
The build of python2.2 fails on arm-linux, trying to start the just
built python executable (building the shared modules). gcc-3.2 and
gcc-snapshot (20030531) are working ok.
$ gdb python
GNU gdb 5.3-debian
Copyright 2002 Free Software Foundatio
Your message dated Wed, 04 Jun 2003 04:17:38 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#52382: fixed in gcc-3.3 1:3.3ds9-3
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 message dated Wed, 04 Jun 2003 04:17:38 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#52382: fixed in gcc-3.3 1:3.3ds9-3
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 message dated Wed, 04 Jun 2003 04:17:38 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#105285: fixed in gcc-3.3 1:3.3ds9-3
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 message dated Wed, 04 Jun 2003 04:17:38 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#195796: fixed in gcc-3.3 1:3.3ds9-3
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 message dated Wed, 04 Jun 2003 04:17:38 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#177433: fixed in gcc-3.3 1:3.3ds9-3
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
Accepted:
cpp-3.3-doc_3.3-3_all.deb
to pool/main/g/gcc-3.3/cpp-3.3-doc_3.3-3_all.deb
cpp-3.3_3.3-3_i386.deb
to pool/main/g/gcc-3.3/cpp-3.3_3.3-3_i386.deb
fastjar_3.3-3_i386.deb
to pool/main/g/gcc-3.3/fastjar_3.3-3_i386.deb
fixincludes_3.3-3_i386.deb
to pool/main/g/gcc-3.3/fixincludes_3.3-3
Accepted:
cpp-3.3_3.3-3_hppa.deb
to pool/main/g/gcc-3.3/cpp-3.3_3.3-3_hppa.deb
fastjar_3.3-3_hppa.deb
to pool/main/g/gcc-3.3/fastjar_3.3-3_hppa.deb
fixincludes_3.3-3_hppa.deb
to pool/main/g/gcc-3.3/fixincludes_3.3-3_hppa.deb
g++-3.3_3.3-3_hppa.deb
to pool/main/g/gcc-3.3/g++-3.3_3.3-3_hppa.
There are disparities between your recently accepted upload and the
override file for the following file(s):
libstdc++5-3.3-dev_3.3-3_i386.deb: package says priority is optional, override
says standard.
Either the package or the override file is incorrect. If you think
the override is correct a
26 matches
Mail list logo
