severity 335286 important merge 335286 323133 thanks On Sat, Oct 22, 2005 at 09:59:30PM -0700, Thomas Bushnell BSG wrote: > 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? Can you give me a pointer to your reasons for leaping to the conclusion that I haven't examined the bug? global-context.cc: In member function 'Moment Global_context::_ZTv0_n24_NK14Global_context7now_momEv() const': global-context.cc:209: internal compiler error: in cp_expr_size, at cp/cp-objcp-common.c:101 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. For Debian GNU/Linux specific bug reporting instructions, see <URL:file:///usr/share/doc/gcc-4.0/README.Bugs>. This is the single most common build failure on arm, hppa, and m68k right now, and has affected literally dozens or hundreds of other packages. I do kinda know it on sight by this point. > 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. That's fine; I had reassigned it to lilypond before I received the mail that you had filed a separate bug there. But this is a duplicate of 323133, so merging. It also is not a release-critical bug because there is a valid workaround for all affected packages, and in spite of the sizeable impact it's non-trivial to fix and has been triaged out of necessity. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature