Testsuite failure

Hi people, I just found out that an earlier message that I sent did not actually get sent. My previous message about testsuite failures didn't make sense because of that. So, I'll just ask my question again. Basically, I have the following problem building GCC 2.95.4: - GCC seems to build fine, no

Bug#151065: marked as done (g++: destructor called twice)

Your message dated Fri, 12 Jul 2002 09:37:52 +0200 with message-id <[EMAIL PROTECTED]> and subject line Not a bug: Re: Bug#151065: g++: destructor called twice 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 th

Bug#151196: gcc-2.95.4-9 ICE in kernel (matroxfb) code

retitle 151196 [fixed in gcc-3.x] gcc-2.95.4-9 ICE in kernel (matroxfb) code tags 151196 + fixed thanks Petr Vandrovec writes: > Package: gcc-2.95 > Version: 2.95.4-9 > > Hi, > I removed debug prints from new matroxfb driver, and ... compiler > died. Simplest example I was able to invent is be

Processed: Re: Bug#151196: gcc-2.95.4-9 ICE in kernel (matroxfb) code

Processing commands for [EMAIL PROTECTED]: > retitle 151196 [fixed in gcc-3.x] gcc-2.95.4-9 ICE in kernel (matroxfb) code Bug#151196: gcc-2.95.4-9 ICE in kernel (matroxfb) code Changed Bug title. > tags 151196 + fixed Bug#151196: [fixed in gcc-3.x] gcc-2.95.4-9 ICE in kernel (matroxfb) code Tags

Processed: Re: Bug#152709: gcc: __VA_ARGS__ stringification crashes preprocessor if __VA_ARGS__ is empty

Processing commands for [EMAIL PROTECTED]: > tags 152709 + fixed Bug#152709: gcc: __VA_ARGS__ stringification crashes preprocessor if __VA_ARGS__ is empty Tags added: fixed > retitle 152709 [fixed in gcc-3.x] __VA_ARGS__ stringification crashes > preprocessor if __VA_ARGS__ is empty Bug#152709:

Bug#151196: gcc-2.95.4-9 ICE in kernel (matroxfb) code

On 12 Jul 02 at 9:22, Matthias Klose wrote: > retitle 151196 [fixed in gcc-3.x] gcc-2.95.4-9 ICE in kernel (matroxfb) code > tags 151196 + fixed > thanks My system still runs 'gcc-2.95.4' when I type 'gcc', so how it comes that you tag this fixed? I could understand 'wontfix', but not 'fixed'.

Bug#152709: gcc: __VA_ARGS__ stringification crashes preprocessor if __VA_ARGS__ is empty

tags 152709 + fixed retitle 152709 [fixed in gcc-3.x] __VA_ARGS__ stringification crashes preprocessor if __VA_ARGS__ is empty reassign 152709 gcc-2.95 thanks Daniel Webb writes: > Package: gcc > Version: 2:2.95.4-14 > Severity: normal > > > -- System Information > Debian Release: 3.0 > Kernel

Bug#152601: gcc-3.0: Dead symlink at /usr/lib/gcc-lib/hppa-linux/3.0.4/libgcc_s.so

Moin, [EMAIL PROTECTED]:~$ dpkg -S /usr/lib/gcc-lib/hppa-linux/3.0.4/libgcc_s.so gcc-3.0: /usr/lib/gcc-lib/hppa-linux/3.0.4/libgcc_s.so [EMAIL PROTECTED]:~$ dpkg -L libgcc1 /. /usr /usr/share /usr/share/doc /usr/share/doc/libgcc1 /usr/share/doc/libgcc1/copyright /usr/share/doc/libgcc1/changelog.D

Processed: Re: Bug#152315: g++-2.95-3/4 template and virtual inheritance bug

Processing commands for [EMAIL PROTECTED]: > retitle 152315 [fixed in g++-3.x] g++-2.95-3/4 template and virtual > inheritance bug Bug#152315: g++-2.95-3/4 template and virtual inheritance bug Changed Bug title. > tags 152315 + fixed Bug#152315: [fixed in g++-3.x] g++-2.95-3/4 template and virtu

Bug#152601: gcc-3.0: Dead symlink at /usr/lib/gcc-lib/hppa-linux/3.0.4/libgcc_s.so

[EMAIL PROTECTED] writes: > Package: gcc-3.0 > Version: 1:3.0.4-7 > Severity: normal > > AIDE reported this dead symlink: > > lrwxrwxrwx1 root root 18 Jul 5 20:16 > /usr/lib/gcc-lib/hppa-linux/3.0.4/libgcc_s.so -> /lib/libgcc_s.so.1 > could you send the output for dpkg -S /

Bug#152709: gcc: __VA_ARGS__ stringification crashes preprocessor if __VA_ARGS__ is empty

Package: gcc Version: 2:2.95.4-14 Severity: normal -- System Information Debian Release: 3.0 Kernel Version: Linux robust.colorado.edu 2.4.17 #1 SMP Sun Apr 21 21:05:15 MDT 2002 i686 unknown Versions of the packages gcc depends on: ii cpp2.95.4-14 The GNU C preprocessor. ii c