Re: how are you kids compiling kernels these days?

[Richard Hector <richard@walnut.gen.nz>]

On 31/05/12 17:37, Paul Johnson wrote:
> On Wed, May 30, 2012 at 11:04 PM, a0z <n@a0z.eu> wrote:
>> On 31/05/12 04:43, Paul Johnson wrote:
>>> I've tried every variation I can think of.
>>>
>>
>> Have you tried "apt-cache search"?
>>
>>
>> a0z@kit:~$ apt-cache search linux 3.2 amd64
>> linux-headers-3.2.0-2-all-amd64 - All header files for Linux 3.2
>> (meta-package)
>> linux-headers-3.2.0-2-amd64 - Header files for Linux 3.2.0-2-amd64
>> linux-headers-3.2.0-2-rt-amd64 - Header files for Linux 3.2.0-2-rt-amd64
>> linux-image-3.2.0-2-amd64 - Linux 3.2 for 64-bit PCs
>> linux-image-3.2.0-2-amd64-dbg - Debugging infos for Linux 3.2.0-2-amd64
>> linux-image-3.2.0-2-rt-amd64 - Linux 3.2 for 64-bit PCs, PREEMPT_RT
>> linux-image-3.2.0-2-rt-amd64-dbg - Debugging infos for Linux
>>
> 
> Thanks, I see same.  Doesn't help, though. What are you typing to get
> the source for the particular packages you see?
> 
> I mean literally, what is at the end of
> 
> $ apt-get source linux-???

It's a while for me too, but IIRC kernel sources are different - you
download the _binary_ package that has the source in it:

linux-source-3.2

Then you can get kernel-package, which has tools to build you a deb from
that source (after you've patched it).

Anything with package with 'amd64' in the name is presumably compiled
for that platform.

Richard