Steve Langasek wrote: > On Mon, Sep 11, 2006 at 03:26:16AM +0200, Fernando Cerezal wrote: >> The package uses gcc to build the module kernel. The latest version of >> gcc in testing is 4.1, but the package needs that gcc be a link to gcc-4.0. >> Otherwise the module builds sucessfully, but it is incompatible with the >> prebuilts Debian kernels [...] > > Or, it uses whatever you specify as a compiler override using the > appropriate environment variables. > > There is no API for passing this information to module packages; you'll have > to do some additional work to set the corresponding compiler version [...]
Is there something I can do as the package maintainer? To put it another way, I was under the impression that it's the user's responsibility to ensure that they're compiling modules with the correct compiler, correct kernel sources and configuration. AFAIK, no other kernel module source package attempts to detect a mismatched compiler version, let alone find the right one. Therefore, if this is a bug, I would say it's a bug in the kernel build system (I'm sure Linus would love to hear that). -- Ciao, Flavio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
