Bug#169233: general: gcc bug on m68k blocks promotion into testing
On Sat, Nov 16, 2002 at 06:25:15PM +0100, Michael Fedrowitz wrote:
> On Fri, Nov 15, 2002 at 04:20:58PM +0100, Yann Dirson wrote:
> > As notified to the people in charge one month ago [1][2], we have a
> > real problem with gcc broken on m68k, preventing new versions of
> > package (esp. e2fsprogs) to enter testing.
> >
> > I submit this as a general bug, since this bug or a similar one has
> > already been reported and marked as "fixed in gcc3" [3][4]. We have
> > to find a solution for this.
>
> Filing critical bugs against general certainly isn't a particularly
> useful way to find a solution... Mailing m68k-build (CCed) instead might
> prove to be a lot more useful. :)
Well, I had posted to debian-68k, which I thought was enough. I was not
aware of this specific alias. Thanks forwarding there.
> Anyway, nearly every such bug I've seen so far could be worked around by
> lowering optimization. I'd try to build e2fsprogs with -O1 or something
> myself, but unfortunately my m68k is currently sitting in some box or
> other. Anyone else wanna take a look at this?
I don't feel that hacking individual packages for this is a long-term
solution. It's more likely that such lowered optimisations will stick there
for some time, even after the gcc problem get solved, and it will be the
users suffering - I'm not sure 68k machines are fast enough to get programs
build with -O1 without someone noticing, though :)
Now there are at least 2 bug reports on m68k/gcc that are tagged as being
fixed in gcc 3.x, so moving m68k to 3.2 right now is maybe the best option.
Unfortunately the enquiry about the feasability status of this option got no
answer...
Regards,
--
Yann Dirson <ydirson@altern.org> | Why make M$-Bill richer & richer ?
Debian-related: <dirson@debian.org> | Support Debian GNU/Linux:
Pro: <yann.dirson@fr.alcove.com> | Freedom, Power, Stability, Gratuity
http://ydirson.free.fr/ | Check <http://www.debian.org/>
Reply to: