Am 18.01.2012 05:05, schrieb Ben Hutchings:
Sorry, I didn't get this. I've downgraded the compiler for the backported kernel to gcc 4.4.On Wed, 2012-01-18 at 03:42 +0000, Ben Hutchings wrote:On Wed, 2012-01-18 at 00:40 +0100, Marcus Osdoba wrote:[...]Now that I finished with building up[...]linux-image-3.1.0-1-486_3.1.8-2~bpo60+1_i386.debThis is wrong; modules built for '3.1.0-1-486' in testing/unstable will not be loadable in a backported kernel due to the compiler version change. (I don't believe that gcc 4.4 and 4.6 are at all incompatible, but the module loader does check this.)[...] Hmm... I think it used to, but I don't see any sign that it does any more. But let's not test this.
Thesis:In general you won't have plain testing-packages if you just use stable+stable-backports. So when compiling the 3.1.8-modules with the same stable gcc (4.4) there is no gcc version mismatch within stable+stable-backports (there is no gcc 4.6...)
So every additonal kernel module (besides those packaged inside linux-image) need to be backported with the same gcc version.
Forgive me, if I got that completly wrong.Anyway, are there any news in the backport upload process? I still use my own packages, but on the server I feel more comfortable with an "official" version where more users may file bugs against.
Thanks for your hard work. Marcus