gcc-3.0 ICE while compiling glibc, march=athlon -ggdb

2001-05-26 Thread Gordon Sadler
3 -march=athlon -ggdb >Severity: critical >Priority: high >Category: c >Class: ice-on-legal-code >Release: 3.0 20010526 (Debian prerelease) (Debian testing/unstable) >Environment: System: Linux debian-home 2.2.19 #1 Sat May 19 16:25:04 CDT 2001 i686 unknown Architectu

Bug#98851: Should have versioned depend on libgcc0?

2001-05-26 Thread Gordon Sadler
Package: gcc-3.0 Version: 1:3.0-0pre010525 Severity: normal libstdc++3 has a versioned depend for libgcc0 I would suggest gcc-3.0 should as well. Currently it is unversioned. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux debian-home 2.2.19 #1 Sat May 19

new gcc packages

2001-05-26 Thread Matthias Klose
Uploaded a new gcc-3.0 package to incoming (2.95.4 and defaults as well). Checked that all the patches for the other archs still apply. If I get enough OK's from the other archs, I'd like to make the next upload priority high, such that it moves fast to testing and replaces the now incompatible ver

Processed: please recheck with recent compiler versions

2001-05-26 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 63546 amaya Bug#63546: mistranslation of amaya on ix86 Bug reassigned from package `gcc' to `amaya'. > thanks Stopping processing here. Please contact me if you need assistance. Darren Benham (administrator, Debian Bugs database)

Processed: forwarded gcc bug

2001-05-26 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > retitle 43170 [PR 40] Result naming doesn't work for functions defined in a > class Bug#43170: Result naming doesn't work for functions defined in a class Changed Bug title. > forwarded 43170 [EMAIL PROTECTED] Bug#43170: [PR 40] Result naming doesn't

Bug#97904: marked as forwarded (gcc-3.0: Pointless moving)

2001-05-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 May 2001 20:39:53 +0200 with message-id <[EMAIL PROTECTED]> has caused the Debian Bug report #97904, regarding gcc-3.0: Pointless moving to be marked as having been forwarded to the upstream software author(s) [EMAIL PROTECTED] (NB: If you are a system administrator and

Bug#95318: marked as forwarded (gcc-3.0: unnecessary cwtl)

2001-05-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 May 2001 20:35:31 +0200 with message-id <[EMAIL PROTECTED]> has caused the Debian Bug report #95318, regarding gcc-3.0: unnecessary cwtl to be marked as having been forwarded to the upstream software author(s) [EMAIL PROTECTED] (NB: If you are a system administrator and

Bug#94974: marked as forwarded (gcj-3.0 does not know that interface members are public by default)

2001-05-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 May 2001 20:22:38 +0200 with message-id <[EMAIL PROTECTED]> has caused the Debian Bug report #94974, regarding gcj-3.0 does not know that interface members are public by default to be marked as having been forwarded to the upstream software author(s) [EMAIL PROTECTED] (N

Bug#94701: marked as forwarded (gcc-3.0: Duplicate loop conditions even with -Os)

2001-05-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 May 2001 20:28:59 +0200 with message-id <[EMAIL PROTECTED]> has caused the Debian Bug report #94701, regarding gcc-3.0: Duplicate loop conditions even with -Os to be marked as having been forwarded to the upstream software author(s) [EMAIL PROTECTED] (NB: If you are a sy

Bug#94404: priorities of gcc-3.0 packages

2001-05-26 Thread Matthias Klose
that get's difficult, because some architectures do use these libraries (and gcc-3.0) as the default. I am unsure if it's worth to reset these priorities, when migrating to 3.0.

Re: Bug in libstdc++3 package

2001-05-26 Thread Ben Collins
On Sat, May 26, 2001 at 02:18:50PM +1000, Sam Couter wrote: > I don't want to put this in the BTS because I *know* gcc-3.0 is beta. > > The libstdc++3 package contains a libtool file /usr/lib/libstdc++.la, which > points libtool at /usr/lib/libstdc++.so, which doesn't exist. > > So, if you've got