severity 322723 important thanks there's a workaround, and gcc-3.4 is known to work as well. Is there any reason to use gcc-4.0 for kernel builds on all architectures?
Frans Pop writes: > I've reassigned this bug from the kernel to gcc-4.0 as we feel that the > solution chosen in the kernel packaging is not really a fix, but a > workaround. > As tests have shown that the problem does not exist when the same kernel > is compiled with gcc-3.3, the real bug is likely in gcc-4.0. > > I've "found" the bug for 4.0.1-3 after looking at the dates for relevant > uploads, but as uploads were quite frequent, I could be off by a version > either way. > > Please see the bug history for details. > > Cheers, > FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
