On Mon, 2005-10-10 at 07:54 -0700, Mark Knecht wrote:
> On 10/10/05, Daniel Segel <[EMAIL PROTECTED]> wrote:
> > Mark Knecht wrote:
> >
> > >I don't know if this was my fault or the make file's fault. uname -r
> > >returned the correct kernel version name, but ivtv's make install file
> > >is using something out of the /usr/src/linux directory.
> > >
> > >
> > >
> > It's fairly common to use the source tree in /usr/src/linux; most
> > programs assume that is the source of the running kernel. If it's not
> > you end up with problems such as you had. It's easy enough to fix with a
> > pair of rm and ln commands.
> >
> > Daniel
> 
> What would your suggestion be for pair of rm and ln commands?
> 
> I get that this was my doing but what's the accepted way of running
> two versions of the same kernel? (In my case UMP and SMP) Am I
> supposed to copy the whole kernel tree to a second directory with a
> different name?
> 
> What bothers me about the ivtv make process was that it said it was
> working with lib/modules/2.6.13-gentoo-r3 but was placing things in
> 2.6.13-gentoo-r3-ht. If the make file knew the right name when it was
> printing on the screen then why didn't it know the right name when it
> was writing files to the hard drive?
> 
> Anyway, I'd like to learn how to do this better. Thanks in advance for
> any insights you can share.

        There is a variable at the top of the linux Makefile (top level) that
sets the "trailing part" of the kernel name.  I would guess it would be
set to "gentoo-r3-ht" in the case you describe. That propagates into
where the kernel Makefile puts the modules.   

        Many extra modules and other things assume that /usr/src/linux is what
contains the sources for your kernel. If you have
a /usr/src/2.6.13-gentoo-r3 as a result of emerging the sources, you
would do

 ln -s /usr/src/2.6.13-gentoo-r3 /usr/src/linux

        My mythtv box is a gentoo system, and I had a lot of trouble originally
getting lirc and ivtv installed. I knew about the /usr/src/linux link,
but the lirc and/or the ivtv ebuild seemed to do a "uname -a" in order
to know what kernel to build for. The net effect was that I had to have
the link, and then reboot before emerging the drivers. 

        At the time I was trying both 2.4 and 2.6 kernels, and it was a pain to
keep changing the links and rebooting.

        Jon
  
> 
> Cheers,
> Mark
> 
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel


_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to