> > > I was unable to run X or any svgalib progs until i recompiled using a
> > > 2.1.X ioport.c. hopefully this will be included in 2.0.35.
> > Build with gcc 2.7.2-* for 2.0 series kernels. That ioport fix is only
> > a small piece
> ack! i disposed of 2.7.2-* long ago. however 2.0.30 seemed very stable
> running with that fix. exactly how small a piece is it-- that is,what
> potential probs might i expect using gcc-2.8.1 for 2.0.X kernel builds?
> thus far 34 seems stable too.
The 2.0.xx kernels have _only_ been tested with gcc-2.7.2.3, and other
combinations are unsupported.
> is this perhaps affecting the firewall ?
In 2.1.xx the changes to fix random breakage of the code under egcs (a
gcc-2.8.x derivative for the most part) were rather extensive and
pervasive... but some may have been just breakage due to new development.
Anyway, nobody is working on fixing 2.0.xx for gcc-2.8.x/egcs. Don't use
them!
Alan, would you be so kind to crash the compilation of 2.0.35 et seq when
the compiler is not 2.7.xxx? Pretty please? These threads tire me...
-- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu