Bug#335286: gcc: Internal error compiling lilypond on hppa

[Thomas Bushnell BSG <tb@becket.net>]

reassign 335286 gcc-4.0
thanks

Steve Langasek <vorlon@debian.org> writes:

> reassign 335286 lilypond
> thanks
>
> On Sat, Oct 22, 2005 at 08:49:17PM -0700, Thomas Bushnell BSG wrote:
>
>> Compiling lilypond 2.6.3-7 on hppa, gcc reports an internal error.
>
>> See:
>> http:://buildd.debian.org/fetch.php?&pkg=lilypond&ver=2.6.3-7&arch=hppa&stamp=1130038470&file=log&as=raw
>
>> Severity serious because this creates an FTBFS situation for lilypond.
>
> Sorry, this is a known bug in gcc that isn't going to be fixed upstream
> until 4.1, and that's still a ways out.  As a workaround, please update
> lilypond to use g++-3.4 when building on arm, hppa, and m68k, as g++-3.4
> doesn't suffer from this particular bug.

How do you know that this is a known bug without knowing what the bug
is?  It does not match the other hppa compilation bug reported, which
manifests itself in incorrect code instead of compilation errors, and
which is hppa-specific, while this one appears on arm too.

Can you give me a pointer to your reasons for leaping to the
conclusion that a bug you haven't examined must be a known bug?

Moreover, this bug should remain filed against gcc-4.0, because it is,
in fact, a bug in gcc 4.0.  There is a *separate* bug filed against
lilypond referring to this one.  This bug should remain open and filed
against gcc-4.0 until a fix is uploaded for Debian.

Thomas