Kernel Compiler missmatches

[Stephan Hermann]

Hi Doko, All,

On Fri, 13 Feb 2009 15:43:35 +0100
Matthias Klose <doko at ubuntu.com> wrote:

> Andy Whitcroft schrieb:
> > There seem to be several simple options here:
> > 
> > 1) expect the users to build their own kernels if they want to use
> >    external modules, or
> > 2) update gcc in -security, and always do so, or
> > 3) have separate kernel builds for each pocket (rather than pocket
> > copying the -security update into -updates, upload it there
> > separatly with a higher upload number).
> > 
> > I guess the security team is best placed to evaluate the safety or
> > otherwise of (2).
> 
> 4) Re-upload gcc-4.2 with the compiler version set back from 4.2.4
>    to 4.2.3, no other changes.
> 
> I don't know the system used to detect the differences for different
> compiler versions, but could it be an option to ignore the subminor
> version number or check for a version greater than?

The problem appears also for vmwaretools modules.

The vmware-config.pl script is crying that the compiler version is
different from the modules compiler version...but after all, if you
force it to compile, it does without a problem.

I think it's a disturbance for users, but regarding that the ABI of
the kernel is not changed it should not be a big problem.

But in the future, we need to ensure, that we have actually the same
gcc version numbers for kernel modules compiled with a gcc or as
proposed in 3) have different kernel packages compiled with the latest
gcc of the pocket.

Regards,

\sh

-- 
Stephan '\sh' Hermann		| OSS Developer &
Systemadministrator JID: sh at linux-server.org	|
http://www.sourcecode.de/ GPG ID: 0xC098EFA8		|
http://leonov.tv/ 3D8B 5138 0852 DA7A B83F  DCCB C189 E733 C098 EFA8