From patchwork Tue Apr 25 05:02:41 2006 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Suur Karu X-Patchwork-Id: 12278 Received: from mail.elion.ee ([194.126.117.142] helo=oma.elion.ee) by www.linuxtv.org with esmtp (Exim 4.50) id 1FYFhk-0003yF-Bv for vdr@linuxtv.org; Tue, 25 Apr 2006 07:03:16 +0200 Received: from [192.168.35.6] ([192.168.35.6]) by oma.elion.ee over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Tue, 25 Apr 2006 08:02:50 +0300 Message-ID: <444DAD71.7090903@fastmail.fm> Date: Tue, 25 Apr 2006 08:02:41 +0300 From: Suur Karu User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: VDR Mailing List References: <01ec01c6675f$e62b9dd0$6401010a@InetX.com> <444D6B15.3090501@gmx.de> In-Reply-To: <444D6B15.3090501@gmx.de> X-OriginalArrivalTime: 25 Apr 2006 05:02:50.0476 (UTC) FILETIME=[80735AC0:01C66825] X-TM-AS-Product-Ver: SMEX-7.0.0.1345-3.52.1006-14406.000 X-TM-AS-Result: No--12.400000-5.000000-31 Subject: [vdr] Re: vdr-remote plugin not compiling??? X-BeenThere: vdr@linuxtv.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: VDR Mailing List List-Id: VDR Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 05:03:16 -0000 Status: O X-Status: X-Keywords: X-UID: 9060 Udo Richter wrote: > Simon Baxter wrote: >> I've just downloaded vdr-remote-0.3.6, and it won't compile. >> >> g++ -fPIC -g -O2 -Wall -Woverloaded-virtual -c >> -DPLUGIN_NAME_I18N='"remote"' -D_GNU_SOURCE -DREMOTE_FEATURE_LIRC >> -DREMOTE_FEATURE_TCPIP -I../../../include >> -I/lib/modules/2.6.16.9/build/include remote.c >> /lib/modules/2.6.16.9/build/include/linux/input.h:801: error: >> 'kernel_ulong_t' does not name a type > > Since this kernel is quite fresh, maybe its an error in the kernel > headers. Try pointing DVBDIR in Make.config to an older kernel header > version. Or, if you upgrade to recent VDR, don't point to kernel headers > at all. Since 1.3.47 VDR defaults to use /usr/include/input.h and similar. Yeah. One workaround founded in vdrportal.de is patching kernel header file input.h SK --- input.h.orig 2006-03-20 21:54:47.000000000 +0100 +++ input.h 2006-03-21 00:28:57.000000000 +0100 @@ -796,6 +796,7 @@ #define FF_MAX 0x7f +#ifdef __KERNEL__ struct input_device_id { kernel_ulong_t flags; @@ -814,6 +815,7 @@ kernel_ulong_t driver_info; }; +#endif /* * Structure for hotplug & device<->driver matching.