[mythtv-users] Slightly OT - re-building an atrpms package

[Ken Smith]

Jarod Wilson wrote:
> On Fri, Jul 23, 2010 at 7:10 PM, Jarod Wilson <jarod at wilsonet.com> wrote:
>   
>> On Fri, Jul 23, 2010 at 5:07 PM, Ken Smith <kens at kensnet.org> wrote:
>>     
>>> Hi, Slightly off topic, but I wonder if someone here can advise me. I need to build a ivtv rpm for
>>> kernel-2.6.18-194.8.1.el5.centos.plus as its not on atrpms (yet) When I run the rpm build I get
>>>
>>> error: line 3: Unknown tag: %kmdl ivtv
>>>
>>> I have brewed up a few rpm's previously but I'm by no means an expert. So I'd appreciate some advice.
>>>       
>> ATrpms uses a few of its own helper macros, which I believe are all
>> available in a package called atrpms-rpm-config.
>>
>> That said, knowing the el5 kernel like I do... You shouldn't actually
>> have to rebuild (most) kernel modules for a new kernel, especially
>> within a z-stream update kernel (kernel-2.6.18-194.8.1.el5 is a
>> z-stream kernel update from the el5.5 ga kernel, 2.6.18-194.el5), as
>> the kabi is strictly maintained. In other words, an existing ivtv.ko
>> on your box from the prior kernel should work just as well as one you
>> rebuild.
>>     
>
> ...however, its possible that non-whitelisted kabi symbols are used
> and it actually does need rebuilding if the non-whitelisted symbols
> have changed... But very unlikely within a z-stream kernel update.
>
>
>   

Thanks Jarod, The helper package worked and I have put the packages I 
built here -> www.kensnet.org/atrpms

I tried using the earlier ivtv.ko but I got some symbol fails. 
Interestingly I copied the earlier nVidia driver file in the same way 
and it worked fine.

Before I got the rpmbuild working I tried a make / make install of the 
ivtv tar.gz that was in the source rpm. It seemed to work and I could 
cat /dev/video0 and get a reasonable .mpg file, but myth wasn't 
interested in working the pvr350. But after I got the v4l rpm built and 
installed myth was happy. Maybe I should have moved some other v4l bits 
over from the previous kernel
and it might have worked.

Thanks

Ken

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.