Your message dated Tue, 10 Nov 2009 10:23:49 +0100
with message-id <200911101023.49768.gud...@gudjon.org>
and subject line libcomedi-dev: Problems with comedilib.h and kernel modules
has caused the Debian Bug report #288290,
regarding libcomedi-dev: Problems with comedilib.h and kernel modules
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
288290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=288290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcomedi-dev
Version: 0.7.22-2
Severity: minor

File comedilib.h contains the following fragment:

#include <sys/ioctl.h>
#include <fcntl.h>
#include <stdio.h>

When comedilib.h is included from a kernel module, the above fragment
causes a compilation error because of various conflicting
definitions. When the fragment is removed, the kernel module compiles
fine. Another way to solve the problem is to include a separate header
file for kernel modules. 



-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-adeos
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)

Versions of packages libcomedi-dev depends on:
ii  libc6-dev                   2.3.2.ds1-18 GNU C Library: Development Librari
ii  libcomedi0                  0.7.22-2     Library for Comedi

-- no debconf information

-- 
All that is gold does not glitter,
Not all those who wander are lost;
The old that is strong does not wither,
Deep roots are not reached by the frost. 



--- End Message ---
--- Begin Message ---
Package: libcomedi-dev
Version: 0.8.1-5

Hi
    Sorry, I missed this bug but I guess it was fixed with version 0.8.1.

Regards
Gudjon


--- End Message ---

Reply via email to