Andrew,

This is likely a side effect of switching versions between different repos.
Please purge (apt-get remove --purge $PACKAGE) all instances of
lirc-modules-source before installing a new one.

On Tue, Mar 25, 2008 at 2:03 PM, Andrew Barbaccia <email address hidden>
wrote:

> err. that's actually what i am in the process of doing right now. building
> lirc0.8.3pre1 seems to be more difficult than cvs (since it is not using
> automake?)
>
> Also, trying to install the lirc-modules-source from your repository does
> not complete. I'm left with this error:
>
> You must run a dkms build for kernel 2.6.24-12-generic (i686) first.
> Done.
>
> Any advice?
>
> On Tue, Mar 25, 2008 at 2:53 PM, Mario Limonciello <email address hidden>
> wrote:
>
> > Andrew,
> >
> > Sounds like a sensible plan of action, but I see a point for failure.
> >  There
> > is a handful of 2.6.24 patches that came after 0.8.3~pre1.
> >
> > Maybe the better idea is to apt-get source lirc, and then dpatch
> > apply-all.
> > Run the standard build process (configure/make not debuild) to make sure
> > nothing in the build system that we have on top is breaking it.
> >
> > On Tue, Mar 25, 2008 at 12:37 PM, Andrew Barbaccia <
> <email address hidden>>
> > wrote:
> >
> > > So here's my plan of action. Let me know your thoughts:
> > >
> > > nstall lirc0.8.3pre1 from source and test sending via lirc_serial
> > > this will determine if it is the package or the source that is broken.
> > if
> > > it
> > > works, then we need to find the differences in the build options to
> get
> > it
> > > building correctly. if it fails, we need to find the patch between
> pre1
> > > and
> > > cvs that corrects the problem and apply.
> > > Test patches on pre1 SOURCE (not package) until we narrow down which
> > patch
> > > makes the fix
> > > Once the patch is determined then we can go ahead and fix the current
> > > package and push it to hardy.
> > >
> > > On Mon, Mar 24, 2008 at 8:32 PM, Mario Limonciello <<email address hidden>
> >
> > > wrote:
> > >
> > > > So it's not in the modules, it is, it's not, it is.  I hate when
> > things
> > > > go in circles like this :)  Hopefully we'll get to the bottom of
> this
> > > > soon.
> > > >
> > > > --
> > > > lirc_serial loads but does not work (Gutsy 7.10 + Hardy 8.04)
> > > > https://bugs.launchpad.net/bugs/182530
> > > > You received this bug notification because you are a direct
> subscriber
> > > > of the bug.
> > > >
> > >
> > >
> > > --
> > > Andrew Barbaccia
> > > MonolithMC Sales & Support
> > > (631) 865 - 1025
> > >
> > > --
> > > lirc_serial loads but does not work (Gutsy 7.10 + Hardy 8.04)
> > > https://bugs.launchpad.net/bugs/182530
> > > You received this bug notification because you are a member of MythTV
> > > Ubuntu Maintainers, which is subscribed to lirc in ubuntu.
> > >
> >
> >
> > --
> > Mario Limonciello
> > <email address hidden>
> >
> > --
> > lirc_serial loads but does not work (Gutsy 7.10 + Hardy 8.04)
> > https://bugs.launchpad.net/bugs/182530
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> --
> Andrew Barbaccia
> MonolithMC Sales & Support
> (631) 865 - 1025
>
> --
> lirc_serial loads but does not work (Gutsy 7.10 + Hardy 8.04)
> https://bugs.launchpad.net/bugs/182530
> You received this bug notification because you are a member of MythTV
> Ubuntu Maintainers, which is subscribed to lirc in ubuntu.
>



-- 
Mario Limonciello
<email address hidden>