Bug#335286: gcc: Internal error compiling lilypond on hppa
tags 335286 - fixed-upstream
tags 335286 + help
thanks
Steve Langasek writes:
> On Sat, Oct 22, 2005 at 11:18:00PM -0700, Thomas Bushnell BSG wrote:
> > I find it ludicrous to think that the best solution here is to force a
> > jillion maintainers to workaround the bug and recompile.
>
> I would be happy to see a patch submitted for g++-4.0 that makes it work
> correctly on arm/hppa/m68k so that we can stop having maintainers do
> busywork. But the busywork can be distributed across the affected
> maintainers, and backporting a gcc patch cannot. If you feel up to the task
> of providing a backport to fix this bug, I would certainly be grateful. At
> any rate, when the decision was made to start building packages with g++-3.4
> on these archs, there was no fix yet upstream for the problem.
unfortunately this one turned out not to be fixed upstream (or it
reappeared).
> > Hrm, seriously though, why not backport the fix (though the upstream
> > bug record doesn't seem to show one yet, while the Debian bug record
> > says fixed-upstream)? Or, failing that, take gcc-4.0 out of use on
> > arm, hppa, and m68k?
>
> If the gcc maintainers think that pointing g++ at g++-3.4 on these archs is
> the best option, I'm game. One disadvantage is that it wouldn't let us get
> feedback about what else might be wrong with g++-4.0 on those architectures,
> but we probably already have all the information we're going to get about
> the current round of toolchain packages.
And we will see other things turning up, which are fixed in 4.0, but
not in 3.4. 3.4 was never really used on any of our
architectures. For the switch to 4.0, all port maintainers were asked
about the new default, so let at least ask them again, if they agree
going back to 3.4 (or forward to 4.1).
Matthias
Reply to: