Bug#220517: linux-kernel-headers: I2C support broken, prevents building several packages
On Thu, Nov 13, 2003 at 05:05:26AM +0200, Martin-Éric Racine wrote:
> Package: linux-kernel-headers
> Version: 2.5.999-test7-bk-9
> Severity: important
>
> For example:
>
> gcc -DHAVE_CONFIG_H -I. -I../../../gfxdrivers/matrox -I../.. -I../../../include -I../../../src -D_REENTRANT -Wall -O3 -ffast-math -pipe -DFUSION_FAKE -Werror-implicit-function-declaration -c ../../../gfxdrivers/matrox/matrox_maven.c -fPIC -DPIC -o matrox_maven.lo
> In file included from ../../../gfxdrivers/matrox/matrox_maven.c:32:
> /usr/include/linux/i2c-dev.h:37: error: field `__user' has incomplete type
Does adding an include of <linux/compiler.h> at the top of i2c-dev.h
fix it?
> /usr/include/linux/i2c-dev.h:37: error: parse error before '*' token
> /usr/include/linux/i2c-dev.h:42: error: field `__user' has incomplete type
> /usr/include/linux/i2c-dev.h:42: error: parse error before '*' token
> /usr/include/linux/i2c-dev.h:44: error: parse error before '}' token
> ../../../gfxdrivers/matrox/matrox_maven.c: In function `maven_write_byte':
> ../../../gfxdrivers/matrox/matrox_maven.c:63: error: implicit declaration of function `i2c_smbus_write_byte_data'
> ../../../gfxdrivers/matrox/matrox_maven.c: In function `maven_write_word':
> ../../../gfxdrivers/matrox/matrox_maven.c:80: error: implicit declaration of function `i2c_smbus_write_word_data'
> ../../../gfxdrivers/matrox/matrox_maven.c: In function `maven_open':
> ../../../gfxdrivers/matrox/matrox_maven.c:311: error: `I2C_SLAVE' undeclared (first use in this function)
> ../../../gfxdrivers/matrox/matrox_maven.c:311: error: (Each undeclared identifier is reported only once
> ../../../gfxdrivers/matrox/matrox_maven.c:311: error: for each function it appears in.)
> ../../../gfxdrivers/matrox/matrox_maven.c: In function `maven_init':
> ../../../gfxdrivers/matrox/matrox_maven.c:450: error: `I2C_SLAVE' undeclared (first use in this function)
> make[4]: *** [matrox_maven.lo] Error 1
>
> Given how libc6-dev has now become dependant upon
> linux-kernel-headers (why the hell wasn't libc6-dev designed to
> accomodate an existing and reliable kernel-headers-2.4.xx to fulfill
> this dependency? ARGH!), I very much have to consider this an
> important bug.
Kindly read any of the hundred explanations of this decision in the
-glibc or -devel archives before ranting about it.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
Reply to: