Re: Compiling lirc-0.7 && Fedora Core 3

[Robert D. <rd...@cs...>]

Sorry,

I take that back.  My compile just failed looking for a file:

  gcc -Wp,-MD,/usr/src/lirc-0.7.0/drivers/lirc_i2c/.lirc_i2c.o.d -nostdinc
-iwithprefix include -D__KERNEL__ -Iinclude  -Wall -Wstrict-prototypes
-Wno-trigraphs -fno-strict-aliasing -fno-common -Os -fomit-frame-pointer
-g -Wdeclaration-after-statement -pipe -msoft-float -m32
-fno-builtin-sprintf -fno-builtin-log2 -fno-builtin-puts
-mpreferred-stack-boundary=2 -fno-unit-at-a-time -march=i686 -mregparm=3
-Iinclude/asm-i386/mach-default -DIRCTL_DEV_MAJOR=61 -DEXPORT_SYMTAB
-DHAVE_CONFIG_H -I. -I. -I../.. -I
/usr/src/lirc-0.7.0/drivers/lirc_i2c/../.. -I
/lib/modules/2.6.9-1.667/build//include/  -DMODULE
-DKBUILD_BASENAME=lirc_i2c -DKBUILD_MODNAME=lirc_i2c -c -o
/usr/src/lirc-0.7.0/drivers/lirc_i2c/.tmp_lirc_i2c.o
/usr/src/lirc-0.7.0/drivers/lirc_i2c/lirc_i2c.c
/usr/src/lirc-0.7.0/drivers/lirc_i2c/lirc_i2c.c:69:41:
../drivers/media/video/bttv.h: No such file or directory

make[6]: *** [/usr/src/lirc-0.7.0/drivers/lirc_i2c/lirc_i2c.o] Error 1
make[5]: *** [_module_/usr/src/lirc-0.7.0/drivers/lirc_i2c] Error 2
make[5]: Leaving directory `/lib/modules/2.6.9-1.667/build'
make[4]: *** [lirc_i2c.o] Error 2
make[4]: Leaving directory `/usr/src/lirc-0.7.0/drivers/lirc_i2c'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/usr/src/lirc-0.7.0/drivers/lirc_i2c'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/lirc-0.7.0/drivers'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/lirc-0.7.0'
make: *** [all] Error 2


I could only find the bttv.h file in the kernel source.  So I still don't
know how you can compile lirc without it.

-Rob


>
> This is the error message I was receiving from configure before I
> installed the kernel source in /usr/src/linux:
>
> configure: error: *** you need to have the Linux kernel source installed
>         for this driver
>
>
> You are right, adding that config parameter also resolved the problem.  I
> was able to 'head config.status' to determine what setup.sh used for my
> configure setup, and add the --with-kerneldir param.
>
> Unfortunately, config.status wasn't created until towards the end of the
> configure script.  So when configure was originally erroring out because
> of the missing kernel source, I had no idea how setup.sh was running
> configure.
>
>
> -Rob
>
>
> > On Tue, Dec 28, 2004 at 09:49:44AM -0500, Robert Dege wrote:
> >
> > > Thanks,
> > >
> > > I found the problem though.  Apparantly, with the new 2.6 kernels, you
> > > need to run make on the source in /usr/src/linux in order to get all the
> > > extra files setup correctly.  I was still accustomed to just running 'make
> > > dep' with the older 2.4 kernels.
> >
> > Ehrm, for Fedora Core 3 you don't actually need to have the kernel
> > source installed. In fact, it's probably a lot more trouble to use the
> > sources in /usr/src/linux/.
> >
> > I've used the --with-kerneldir option a gazillion times and it always
> > worked...
> >
> > armijn
> >
> > --
> >  ---------------------------------------------------------------------------
> >   ar...@uu... | http://www.uulug.nl/ | UULug: Utrecht Linux Users Group
> >  ---------------------------------------------------------------------------
> >
>
>
>
> Dege
>
> As seen on bash.org:
> The problem with America is stupidity. I'm not saying there
> should be a capital punishment for stupidity, but why don't
> we just take the safety labels off of everything and let
> the problem solve itself?
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
>



Dege

As seen on bash.org:
The problem with America is stupidity. I'm not saying there
should be a capital punishment for stupidity, but why don't
we just take the safety labels off of everything and let
the problem solve itself?