From: Moofie <mo...@sh...> - 2010-04-30 07:46:54
|
Hi, I have gone through the documentation on the lirc.org site and grepped/skimmed the included files in the source tarball. I cannot find a way to compile multiple drivers for lirc. The system I'm trying to set up has two mceusb transceivers, one commandir transceiver and an imon_vfd receiver. While I run Debian, the package has gone stale in the distribution and I'm wondering how I can go about compiling what I need. I can RTFM, if you have a link for me. Thanks in advance. |
From: Jarod W. <ja...@wi...> - 2010-04-30 14:52:10
|
On Fri, Apr 30, 2010 at 3:46 AM, Moofie <mo...@sh...> wrote: > Hi, > > I have gone through the documentation on the lirc.org site and > grepped/skimmed the included files in the source tarball. I cannot find > a way to compile multiple drivers for lirc. > > The system I'm trying to set up has two mceusb transceivers, one > commandir transceiver and an imon_vfd receiver. While I run Debian, the > package has gone stale in the distribution and I'm wondering how I can > go about compiling what I need. > > I can RTFM, if you have a link for me. TFM: http://lirc.org/html/install.html#compiling :) -- Jarod Wilson ja...@wi... |
From: Moofie <mo...@sh...> - 2010-04-30 15:53:14
|
On 04/30/2010 07:24 AM, Jarod Wilson wrote: > On Fri, Apr 30, 2010 at 3:46 AM, Moofie<mo...@sh...> wrote: >> Hi, >> >> I have gone through the documentation on the lirc.org site and >> grepped/skimmed the included files in the source tarball. I cannot find >> a way to compile multiple drivers for lirc. >> >> The system I'm trying to set up has two mceusb transceivers, one >> commandir transceiver and an imon_vfd receiver. While I run Debian, the >> package has gone stale in the distribution and I'm wondering how I can >> go about compiling what I need. >> >> I can RTFM, if you have a link for me. > > TFM: > > http://lirc.org/html/install.html#compiling > > :) > Hmm, I've tried that, it fails the all target. I will go try it delving into it much deeper. The user-space option isn't what I want, as I want the kernel modules to be built. Thanks! |
From: Jarod W. <ja...@wi...> - 2010-04-30 18:32:11
|
On Fri, Apr 30, 2010 at 11:53 AM, Moofie <mo...@sh...> wrote: > On 04/30/2010 07:24 AM, Jarod Wilson wrote: >> On Fri, Apr 30, 2010 at 3:46 AM, Moofie<mo...@sh...> wrote: >>> Hi, >>> >>> I have gone through the documentation on the lirc.org site and >>> grepped/skimmed the included files in the source tarball. I cannot find >>> a way to compile multiple drivers for lirc. >>> >>> The system I'm trying to set up has two mceusb transceivers, one >>> commandir transceiver and an imon_vfd receiver. While I run Debian, the >>> package has gone stale in the distribution and I'm wondering how I can >>> go about compiling what I need. >>> >>> I can RTFM, if you have a link for me. >> >> TFM: >> >> http://lirc.org/html/install.html#compiling >> >> :) >> > > Hmm, I've tried that, it fails the all target. I will go try it delving > into it much deeper. The user-space option isn't what I want, as I want > the kernel modules to be built. You could just do multiple build/install cycles to get all three then. If the all target is failing, it would be nice to know exactly how, as that *is* expected to work. -- Jarod Wilson ja...@wi... |
From: Dale P. <DEP...@ed...> - 2010-04-30 21:05:32
|
On 04/30/10 14:31, Jarod Wilson wrote: > On Fri, Apr 30, 2010 at 11:53 AM, Moofie <mo...@sh...> wrote: >> On 04/30/2010 07:24 AM, Jarod Wilson wrote: >>> On Fri, Apr 30, 2010 at 3:46 AM, Moofie<mo...@sh...> wrote: >>>> Hi, >>>> >>>> I have gone through the documentation on the lirc.org site and >>>> grepped/skimmed the included files in the source tarball. I cannot find >>>> a way to compile multiple drivers for lirc. >>>> >>>> The system I'm trying to set up has two mceusb transceivers, one >>>> commandir transceiver and an imon_vfd receiver. While I run Debian, the >>>> package has gone stale in the distribution and I'm wondering how I can >>>> go about compiling what I need. >>>> >>>> I can RTFM, if you have a link for me. >>> >>> TFM: >>> >>> http://lirc.org/html/install.html#compiling >>> >>> :) >>> >> >> Hmm, I've tried that, it fails the all target. I will go try it delving >> into it much deeper. The user-space option isn't what I want, as I want >> the kernel modules to be built. > > You could just do multiple build/install cycles to get all three then. > > If the all target is failing, it would be nice to know exactly how, as > that *is* expected to work. > I'm in this boat, and that's what I do - build, change the target, build, etc. I guess I should try "all" again to give you a decent error report. On the other hand, I've grown sufficiently frustrated with my imon VFD that I'm not using it now, just the cheapo mceusb, so I no longer need multiple drivers. The imon vfd appears to have hardware/electrical problems - it can slow getting through the bios to a crawl - I suspect timeouts. One of these days I'll look harder at it - no time right now. Dale Pontius |
From: Moofie <mo...@sh...> - 2010-05-16 07:53:31
Attachments:
lirc-error.txt
|
On 04/30/2010 11:31 AM, Jarod Wilson wrote: > On Fri, Apr 30, 2010 at 11:53 AM, Moofie<mo...@sh...> wrote: >> On 04/30/2010 07:24 AM, Jarod Wilson wrote: >>> On Fri, Apr 30, 2010 at 3:46 AM, Moofie<mo...@sh...> wrote: >>>> Hi, >>>> >>>> I have gone through the documentation on the lirc.org site and >>>> grepped/skimmed the included files in the source tarball. I cannot find >>>> a way to compile multiple drivers for lirc. >>>> >>>> The system I'm trying to set up has two mceusb transceivers, one >>>> commandir transceiver and an imon_vfd receiver. While I run Debian, the >>>> package has gone stale in the distribution and I'm wondering how I can >>>> go about compiling what I need. >>>> >>>> I can RTFM, if you have a link for me. >>> >>> TFM: >>> >>> http://lirc.org/html/install.html#compiling >>> >>> :) >>> >> >> Hmm, I've tried that, it fails the all target. I will go try it delving >> into it much deeper. The user-space option isn't what I want, as I want >> the kernel modules to be built. > > You could just do multiple build/install cycles to get all three then. > > If the all target is failing, it would be nice to know exactly how, as > that *is* expected to work. > My apologies on the very delayed response. I've been running around trying to find people with similar issues and I cannot specifically figure out the problem. Alas I give up, I can't find a way to fix it. It stems from having linux-2.6.32 as the base kernel to compile against. That seems to be the only commonality between what google can tell me and what I've been experiencing. There are also messages on the Debian BTS stating that the lirc_gpio sub module is abandoned and broken with newer kernels (after 2.6.24) I am attaching the output that make pumps out (related to the errors). my configure command is: ./configure --with-kerneldir=/usr/src/linux-headers-2.6.32-5-amd64 --with-driver=all --with-moduledir=/lib/modules/`uname -r`/misc --without-x Let me know if I can provide any more information. |
From: <li...@ba...> - 2010-05-19 17:21:04
|
Hi! Moofie "mo...@sh..." wrote: [...] >> If the all target is failing, it would be nice to know exactly how, as >> that *is* expected to work. >> > My apologies on the very delayed response. I've been running around > trying to find people with similar issues and I cannot specifically > figure out the problem. Alas I give up, I can't find a way to fix it. > > It stems from having linux-2.6.32 as the base kernel to compile against. > That seems to be the only commonality between what google can tell me > and what I've been experiencing. > > There are also messages on the Debian BTS stating that the lirc_gpio sub > module is abandoned and broken with newer kernels (after 2.6.24) Yes, it is broken and you probably don't need it. So you don't have to compile it. I've also just removed it from the --with-driver=all setup. Christoph |
From: Moofie <mo...@sh...> - 2010-05-19 17:37:53
|
On 05/19/2010 10:19 AM, Christoph Bartelmus wrote: > Hi! > > Moofie "mo...@sh..." wrote: > [...] >>> If the all target is failing, it would be nice to know exactly how, as >>> that *is* expected to work. >>> > >> My apologies on the very delayed response. I've been running around >> trying to find people with similar issues and I cannot specifically >> figure out the problem. Alas I give up, I can't find a way to fix it. >> >> It stems from having linux-2.6.32 as the base kernel to compile against. >> That seems to be the only commonality between what google can tell me >> and what I've been experiencing. >> >> There are also messages on the Debian BTS stating that the lirc_gpio sub >> module is abandoned and broken with newer kernels (after 2.6.24) > > Yes, it is broken and you probably don't need it. So you don't have to > compile it. > > I've also just removed it from the --with-driver=all setup. > > Christoph > > ------------------------------------------------------------------------------ > > Perfect thank you, I will grab a copy of the source later tonight to try it. I was just about to re-send an email that was held for moderation as my attached output exceeded the 20k limit. So this fixes that as well. Thanks again. |
From: Ryan V. <sim...@si...> - 2010-05-16 13:46:50
|
Moofie said: > On 04/30/2010 11:31 AM, Jarod Wilson wrote: > > My apologies on the very delayed response. I've been running around > trying to find people with similar issues and I cannot specifically > figure out the problem. Alas I give up, I can't find a way to fix it. > > It stems from having linux-2.6.32 as the base kernel to compile against. > That seems to be the only commonality between what google can tell me > and what I've been experiencing. > > There are also messages on the Debian BTS stating that the lirc_gpio sub > module is abandoned and broken with newer kernels (after 2.6.24) > > I am attaching the output that make pumps out (related to the errors). > > my configure command is: > > ./configure --with-kerneldir=/usr/src/linux-headers-2.6.32-5-amd64 > --with-driver=all --with-moduledir=/lib/modules/`uname -r`/misc --without-x > > Let me know if I can provide any more information. > Honestly the errors i saw looked like the driver needs the full kernel source and not just the headers, since i believe the headers are usually just the include directory in the kernel. This driver appears to be loading .h files directly from the bttv driver in the kernel, you might try installing the full kernel source for your distro (don't remember how on debian myself). |
From: Moofie <mo...@sh...> - 2010-05-18 08:10:26
Attachments:
lirc-error-gpio.txt
|
On 05/16/2010 05:44 AM, Ryan Voots wrote: > Moofie said: >> On 04/30/2010 11:31 AM, Jarod Wilson wrote: >> >> My apologies on the very delayed response. I've been running around >> trying to find people with similar issues and I cannot specifically >> figure out the problem. Alas I give up, I can't find a way to fix it. >> >> It stems from having linux-2.6.32 as the base kernel to compile against. >> That seems to be the only commonality between what google can tell me >> and what I've been experiencing. >> >> There are also messages on the Debian BTS stating that the lirc_gpio sub >> module is abandoned and broken with newer kernels (after 2.6.24) >> >> I am attaching the output that make pumps out (related to the errors). >> >> my configure command is: >> >> ./configure --with-kerneldir=/usr/src/linux-headers-2.6.32-5-amd64 >> --with-driver=all --with-moduledir=/lib/modules/`uname -r`/misc --without-x >> >> Let me know if I can provide any more information. >> > > Honestly the errors i saw looked like the driver needs the full kernel source and not just the headers, since i believe the headers are usually just the include directory in the kernel. This driver appears to be loading .h files directly from the bttv driver in the kernel, you might try installing the full kernel source for your distro (don't remember how on debian myself). > > ------------------------------------------------------------------------------ > > I hear what you're saying, but unless I'm completely daft (I fixed my configure line :) it's pointing to the right place. What it looks like, is that I don't understand what I'm doing at this point. Some of the supporting source builds, some drivers build, then it hits the gpio driver. It dies. Here's the newest output I have as a result from make (I'm attaching the full output). |