Re: gcc-2.95 bugs on m68k: what to do ?
Richard Zidlicky writes:
> On Tue, Oct 29, 2002 at 06:10:57PM +0100, Yann Dirson wrote:
> > On Mon, Oct 21, 2002 at 09:43:05PM +0200, Matthias Klose wrote:
> > > Yann Dirson writes:
> > > > I have several packages (e2fsprogs, bigloo) that fail to build on
> > > > m68k, apparently due to one or more gcc bug(s). Maybe that's the same
> > > > as #146006, and #89023, but I can't tell that myself.
> > > >
> > > > Madkiss suggested forcing the use of gcc-3.2. But if this compiler is
> > > > officially broken on m68k, I'd rather not change those packages and
> > > > have the autobuilders use gcc-3.2 at least for m68k...
it is "broken", because you don't get enough testsuite failures not to
hit the buildd timeout ... I'm working on a fix.
> > > > What about changing build-essential list to make gcc-3.2 the default
> > > > on m68k ?
> would be the best solution imho.
let's make this at one point for all architectures. just waiting for
the m68k build ...
> > > AFAIK, the needed libgcc1-compat library is not yet built for m68k
> > > (CCing the glibc people)
> > Anything new here ?
this is not strictly necessary for the gcc transition, but is required
for the glibc-2.2 -> 2.3 transition.