linux-2.6.8-rc2-love3 - problems compiling lirc_i2c.o

[Mochakree]

I am having strange problems compiling the lirc_i2c module that is patched into the love sources. I installed the source with the ebuild on the love website and have tried compiling with both genkernel and manually, both result in the error below.

My machine currently has a 2.6.7 development sources kernel. I chose to switch to love specifically because I need the lirc_i2c module to make my hauppauge pvr remote function. So I can't just not select this module.

Does anyone know what caused this error and how I can fix it?

CC drivers/block/cryptoloop.o
LD drivers/block/built-in.o
CC drivers/cdrom/cdrom.o
LD drivers/cdrom/built-in.o
CC drivers/char/mem.o
CC drivers/char/random.o
CC drivers/char/tty_io.o
CC drivers/char/n_tty.o
CC drivers/char/tty_ioctl.o
CC drivers/char/pty.o
CC drivers/char/misc.o
LD drivers/char/agp/built-in.o
CC [M] drivers/char/agp/backend.o
CC [M] drivers/char/agp/frontend.o
CC [M] drivers/char/agp/generic.o
CC [M] drivers/char/agp/isoch.o
LD [M] drivers/char/agp/agpgart.o
CC [M] drivers/char/agp/nvidia-agp.o
LD drivers/char/drm/built-in.o
CC [M] drivers/char/drm/gamma_drv.o
CC [M] drivers/char/drm/gamma_dma.o
CC [M] drivers/char/drm/r128_drv.o
CC [M] drivers/char/drm/r128_cce.o
CC [M] drivers/char/drm/r128_state.o
CC [M] drivers/char/drm/r128_irq.o
CC [M] drivers/char/drm/radeon_drv.o
CC [M] drivers/char/drm/radeon_cp.o
CC [M] drivers/char/drm/radeon_state.o
CC [M] drivers/char/drm/radeon_mem.o
CC [M] drivers/char/drm/radeon_irq.o
CC [M] drivers/char/drm/tdfx_drv.o
LD [M] drivers/char/drm/gamma.o
LD [M] drivers/char/drm/tdfx.o
LD [M] drivers/char/drm/r128.o
LD [M] drivers/char/drm/radeon.o
LD drivers/char/lirc/built-in.o
CC [M] drivers/char/lirc/lirc_dev.o
CC [M] drivers/char/lirc/lirc_i2c.o
drivers/char/lirc/lirc_i2c.c: In function `add_to_buf_pcf8574':
drivers/char/lirc/lirc_i2c.c:137: error: structure has no member named `c'
drivers/char/lirc/lirc_i2c.c: In function `add_to_buf_haup':
drivers/char/lirc/lirc_i2c.c:170: error: structure has no member named `c'
drivers/char/lirc/lirc_i2c.c: In function `add_to_buf_pixelview':
drivers/char/lirc/lirc_i2c.c:203: error: structure has no member named `c'
drivers/char/lirc/lirc_i2c.c:212: error: invalid type argument of `unary *'
drivers/char/lirc/lirc_i2c.c:212: error: `b' undeclared (first use in this func
ion)
drivers/char/lirc/lirc_i2c.c:212: error: (Each undeclared identifier is reporte
only once
drivers/char/lirc/lirc_i2c.c:212: error: for each function it appears in.)
drivers/char/lirc/lirc_i2c.c: In function `add_to_buf_pv951':
drivers/char/lirc/lirc_i2c.c:223: error: structure has no member named `c'
drivers/char/lirc/lirc_i2c.c: In function `add_to_buf_knc1':
drivers/char/lirc/lirc_i2c.c:248: error: structure has no member named `c'
make[3]: *** [drivers/char/lirc/lirc_i2c.o] Error 1
make[2]: *** [drivers/char/lirc] Error 2
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2
_________________
Genius may have its limitations, but stupidity is not thus handicapped.
- Elbert Hubbard

-Craig Meyer

[butters]

Took a look at the source code, you're not doing anything wrong, this is simply bad code...

On all the lines reporting no member 'c', there are references to a field c in the i2c_ir struct. These instances of 'c' should probably be changed to 'client', which is a valid field in that struct.

If this was the only problem, I would recommend just changing the code and recompiling, but also theres an assignment *key=b, where key is an unsigned char pointer, and there is no variable b in the scope. What this should be changed to is ambiguous, either *key=0xb, *key='b', or *key=&buf would be equally likely, since I have no particular knowledge about this code.

Therefore you should try another kernel source with lirc, I recommend nitro-sources:
https://forums.gentoo.org/viewtopic.php?t=207056

Very similar to love-sources, except with CK's staircase scheduler instead of Nick's v130g scheduler. I get *much* better performance with nitro-sources, so I urge you to go ahead and try that. Hopefully it doesn't use the same broken patch. Same procedure as with love-sources: create a directory in your portage overlay to put the ebuild, then ebuild /path/to/nitro-sources???.ebuild digest, emerge nitro-sources, and you're ready to configure and compile!!

Note: genkernel ONLY support the gentoo-sources 2.4.x kernels.
_________________
If tugboats were bigger, they'd be the ones getting tugged.

[Mochakree]

I appreciate the help that you provided so far, however the nitro-sources don't seem to be the solution to my problem. I downloaded them and ran make menuconfig. When selecting the device support that I required I found that though the sources have lirc support, they don't seem to have support for the i2c version of the driver. Do you know of another kernel that might have what I need? Alternatively, I believe I could always fall back on an earlier version of the love sources.[/i]
_________________
Genius may have its limitations, but stupidity is not thus handicapped.
- Elbert Hubbard

-Craig Meyer

[morck]

You could just try to emerge lirc. The latest version 0.7.0_pre7 has support for building modules even with 2.6 kernel and does not depend on any special kernel-sources.

[Mochakree]

Hmmm... I noticed when I emerged 0.7.0_pre7 (even before I started this topic) that the warning message about needing a pached kernel went away. However, I believe I need the lirc_i2c module to make everything work. At the very least, this wasn't compiled by default when I emerged 0.7.0_pre7. Do you know where I can find some documentation on how to get this module using 0.7.0_pre7?

-Craig
_________________
Genius may have its limitations, but stupidity is not thus handicapped.
- Elbert Hubbard

-Craig Meyer