> 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...)" > and then uses "M(str)" without "args".
I compiled Kernel 2.6.13.2 and some extern drivers without any problems! Only ivtv failed to compile. > > 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. You said it, I totally agree. I contribute some packages for LinVDR, a small woody-based Linux specialized for the VDR program. VDR itself and some dozen plugins are all compiled with 2.95, so I can`t come and contribute a plugin compiled with gcc 3.x. Hans, why is it not possible to simply add some ", 0" in a few lines ? Will this have any disadvantegeous effect when it is compiled with an up-to-date compiler? If so, I suggest to add a patch for the "Woodys". If not, please simply add it as suggested. _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
