On Friday 07 October 2005 01:16, Leonard Orb wrote:
> Hans Verkuil wrote:
> > This usage is all over the place in the kernel and in fact also in the
> > video4linux repository. So I am hesitant to add workarounds for what is
> > by now a really old compiler. It is impossible to upgrade to a newer
> > compiler? Once we start using the tuner module etc. from the video4linux
> > repository you will need a new compiler anyway since that won't compile
> > with gcc-2.95 (for pretty much the same reason probably).
>
> Gcc 2.95 will compile kernels up to 2.6.12.6 and probably also newer ones
> without problems, because no one there does "#define M(format, args...)"
This certainly happens in 2.6.13. See e.g. drivers/scsi/ch.c. So this would
mean that a gcc-2.95 can no longer compile the scsi subsystem. And this is
certainly not the only place where this construct is used.
Hans
> And yes, it is not easy to upgrade the compiler with Debian Woody and yes,
> there are reasons not to do it even if you are willing to, e.g. because it
> can cause very nasty errors if you have some modules of some sources
> compiled with 2.95, change some sources or some config and then compile
> some modules with gcc 3.x. Woody's qpopper, fetchmail, innd and other
> packets are really old ones, mplayer is not included and so on, so it is
> likely that users of Woody have had to compile some stuff theirselves and
> after a compiler upgrade they would have to do all this again or think
> about the gcc version mix-up in case of changes. It is living hell.
>
> All this can be as complex as upgrading to Sarge. If someone wants more
> elaborate instructions for an upgrade from Woody to Sarge than that on
> the Debian site: mail me. Sarge comes with gcc 3.3.5.
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
