Le 20/02/2011 15:01, Ben Hutchings a écrit :
> On Sun, 2011-02-20 at 13:52 +0100, Brice Goglin wrote:
>   
>> Le 15/02/2011 04:33, Debian Bug Tracking System a écrit :
>>     
>>>> Hello,
>>>>         
>>>>> linux-headers-2.6.37-trunk-common misses scripts/basic/Makefile.
>>>>> This file is needed by scripts/Makefile.build. For instance,
>>>>> it breaks "make kernelrelease" which makes external module build
>>>>> harder.
>>>>>
>>>>>  $ make kernelrelease -C /lib/modules/2.6.37-trunk-amd64/build
>>>>>  make: Entering directory `/usr/src/linux-headers-2.6.37-trunk-amd64'
>>>>>  /usr/src/linux-headers-2.6.37-trunk-common/scripts/Makefile.build:44:
>>>>>   /usr/src/linux-headers-2.6.37-trunk-common/scripts/basic/Makefile: No 
>>>>> such file or directory
>>>>>  make[4]: *** No rule to make target 
>>>>> `/usr/src/linux-headers-2.6.37-trunk-common/scripts/basic/Makefile'.  
>>>>> Stop.
>>>>>  make[3]: *** [scripts_basic] Error 2
>>>>>  2.6.37
>>>>>  make: Leaving directory `/usr/src/linux-headers-2.6.37-trunk-amd64'
>>>>>           
>>>>     
>>>>         
>>> [...]
>>>
>>> You need to pass M=<your-module-directory> (in fact M=dummy will work).
>>> You can get away without it for some targets, but in general you should
>>> assume this is required.
>>>   
>>>       
>> Hello Ben,
>>
>> Thanks for the hint. Indeed it avoids the problem.
>>
>> However, make kernelrelease returns 2.6.37 instead of 2.6.37-smp-amd64
>> now, so it looks like we have another problem but I am not sure where.
>>     
> Why do you even care what the version is?

I can live without it. One case that I remember of is when you want to
check that the kernel headers match what's installed in /lib/modules. It
doesn't matter for Debian packages. But it matters when you build your
own kernel from a source dir whose version may increase while some old
/lib/modules/ still point to it.

make kernelrelease and /lib/modules/<version> matched in the past, and
they match when installing an upstream kernel manually. It'd be easier
if they match in Debian packages too. If it's not possible anymore, just
say it, I'll use something else :)

thanks
Brice




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to