Re: [opencbm-user] Errors compiling opencbm on Linux.

[<gr...@gm...>]

Hello,

Spiro Trikaliotis wrote:
> Is there a config.h nor the autoconf.h file in the linux/ directory?
> That is, in /usr/src/linux/include/linux/?

Yes, there is autoconf.h:

luca@c65:/usr/src/linux/include/linux$ ll | grep auto
-rw-r--r--  1 root root  44263 2007-07-14 11:11 autoconf.h

> Are the headers exactly the ones used for you running machine?

Yes.

> 
> Please, give me the following info:
> 
> 1. The output of uname -a, and of uname -r

luca@c65:/usr/src/linux/include/linux$ uname -a
Linux c65 2.6.20 #5 PREEMPT Sat Jul 14 11:14:11 CEST 2007 i686 GNU/Linux
luca@c65:/usr/src/linux/include/linux$ uname -r
2.6.20


> 2. The names of ALL installed debian packages that start with linux-...
>    You may get this info from aptitude.

luca@c65:/usr/src/linux/include/linux$ dpkg -l | grep linux
ii  libselinux1                          2.0.15-2+b1 
SELinux shared libraries
ii  libselinux1-dev                      2.0.15-2+b1 
SELinux development headers
ii  linux-kbuild-2.6.22                  2.6.22-1 
Kbuild infrastructure for Linux 2.6.22
ii  linux-libc-dev                       2.6.22-5 
Linux Kernel Headers for development
ii  linux-sound-base                     1.0.15-1 
base package for ALSA and OSS sound systems
ii  linux-source-2.6.18                  2.6.18.dfsg.1-12 
Linux kernel source for version 2.6.18 with
ii  linux-source-2.6.20                  2.6.20-2 
Linux kernel source for version 2.6.20 with
ii  linuxdoc-tools                       0.9.21-0.11 
convert LinuxDoc SGML source into other form
ii  linuxdoc-tools-latex                 0.9.21-0.11 
LaTeX/PS/PDF output facility of LinuxDoc-Too
ii  linuxdoc-tools-text                  0.9.21-0.11 
Text output facility of LinuxDoc-Tools
ii  util-linux                           2.13-9 
Miscellaneous system utilities
ii  util-linux-locales                   2.13-9 
Locales files for util-linux
luca@c65:/usr/src/linux/include/linux$

Greetings,
Luca


p.s. The patch number 1722924 seems to be regarding this error, but it 
also seems to be committed already to the "0.4.0 bug fix branch" tagged 
version.