reassign 327780 m68k thanks that's unreproducible on crest/sid, although I can reproduce it on another machine with the very same versions of gcc-4.0 and libc6. So why not file it for libc6?
The point of reassigning the report to an unknown package is to ask, if it's time to drop m68k from the release architectures or just set the severity of all m68k reports to wishlist. There's currently nobody interested in forwarding m68k related bug reports upstream and testing m68k compiler versions. There are at least six more unhandled m68k reports. My email from July (http://lists.debian.org/debian-release/2005/07/msg00069.html) is left unanswered, so I have to assume, that m68k isn't supported anymore and will start to downgrade all m68k related reports to a non-RC severity. Matthias Wouter Verhelst writes: > Package: gcc-4.0 > Version: 4.0.1-6 > Severity: grave > Justification: renders package unusable > > Hi, > > Script started on Mon Sep 12 08:22:21 2005 > [EMAIL PROTECTED]: /home/wouter~$ cat >foo.c > int main() { > ; > return 0; > } > [EMAIL PROTECTED]:~$ gcc -o foo foo.c > [EMAIL PROTECTED]:~$ ./foo > Segmentation fault > [EMAIL PROTECTED]:~$ > > Since this is exactly what configure-scripts try to compile to see > whether the C compiler works, nothing will compile on m68k anymore. > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing') > Architecture: m68k > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.4.27-mvme16x > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Versions of packages gcc-4.0 depends on: > ii binutils 2.16.1cvs20050902-1 The GNU assembler, linker and > bina > ii cpp-4.0 4.0.1-6 The GNU C preprocessor > ii gcc-4.0-base 4.0.1-6 The GNU Compiler Collection > (base > ii libc6 2.3.5-6 GNU C Library: Shared libraries > an > ii libgcc2 4.0.1-6 GCC support library > > Versions of packages gcc-4.0 recommends: > ii libc6-dev 2.3.5-6 GNU C Library: Development > Librari > pn libmudflap0-dev <none> (no description available) > > -- no debconf information > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
