|
From: Dik T. <D.H...@ph...> - 2004-01-05 18:54:11
|
On Mon, 5 Jan 2004, Richard Ellis wrote:
> On Mon, Jan 05, 2004 at 08:35:31AM -0800, Steven M. Schultz wrote:
> >
> > On Mon, 5 Jan 2004, Dik Takken wrote:
> >
> > > Will version 1.6.2 be compilable on gcc 2.96? I have posted problem
> > > reports about 1.6.1, which appears to be compilable only on gcc 3.x.
> >
> > gcc 2.95.{3,4} was able to compile mjpegtools 1.6.1 without any
> > problems. On some of my systems I use 2.95.3 to build the cvs
> > version of mjpegtools - works fine.
> >
> > Which system is still using 2.96? That was a troublesome version
> > of the compiler (I recall MPlayer being miscompiled by gcc 2.96).
>
> No one should be using 2.96. That was never an official gcc release,
> but instead was a redhat invention (which redhat release I do not
> know) made by pulling a cvs copy of gcc and "labeling" it 2.96. It
> miscompiled lots of stuff, and it was/is object code incompatible
> with everything but itself. We should not expend any more than
> minimal effort worrying about it, because the only true correct
> answer to anyone still using it is properly "upgrade".
>
Yes I know 2.96 is evil :) but I never had any problems with it. I have
used it to compile multiple generations of Linux kernels, XFree, KDE,
MPlayer. All of these have always been running rock-solid.
The real pain is that I have to do a complete re-install of my from
top-to-bottom customized installation if I want to get rid of that
stupid gcc 2.96....
But if I am the only one with this compile problem, I understand your
decision to not do anything about it.
Dik
|