It is much easier than in my previous message to get plugins running,
that use cReadDir:
add
DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE \
-D_LARGEFILE64_SOURCE
to Make.config
Regards,
Johann
___
vdr mailing list
vdr@linuxtv.org
http://www.
> Date: Mon, 12 Jan 2009 23:43:33 +0100
> From: rni...@gmx.de
> To: vdr@linuxtv.org
> Subject: [vdr] [ANNOUNCE] vdr-xine-0.9.0 plugin
>
> Hi,
>
> after being away 7 month from VDR development I'm pleased to
> announce release 0.9.0. You can find it on my homepage as usual:
>
Welcome back - man
>> I'm trying to install xineliboutput on a EPIA SP13000, but am getting the
>> following error:
>>
>> [r...@freddy xineliboutput-1.0.3]# make install
>> Makefile:68:
>> Makefile:69: xine-lib not detected ! frontends will not be compiled.
>>
> I usually start by installing the latest version of ubuntu on one
> computer and then duplicate that directory for every client.
Completely diskless clients booting through PXE or iSCSI from
single image or from dedicated images from server are also worth to try.
This work fast on gi
Andrey Kuzmin wrote:
>> I usually start by installing the latest version of ubuntu on one
>> computer and then duplicate that directory for every client.
>>
>
> Completely diskless clients booting through PXE or iSCSI from
> single image or from dedicated images from server are also
On 14.01.2009 02:48, LinHai wrote:
> when I start the VDR-PC,The Screen displays:
> /usr/bin/runvdr:line 576: 4515 Segmentation fault
Line 576 is in my latest patched runvdr extreme 0.4.0 release the line
in which the actual VDR process is launched, at least if you're using
the runvdr-0.4.0-xserve
Hi,
Joerg Riechardt schrieb:
> I tried with vdr-1.6.0.2 and got messages "trying to connect" or so, but
> never a connect. I used the added xine-lib (+ patch) and -ui under Suse
> 11.1. vdr-xine-0.8.2 works well. As I have no X I use fbxine.
Couldn't reproduce this issue. fbxine worked with vd
Hi.
I'm having problems compiling VDR 1.7.0 and 1.7.3.
This is the error:
/usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:64:28:
error: linux/compiler.h: No such file or directory
In file included from
/usr/local/src/s2-liplianin/linux/include/linux/videodev.h:16,
fr
On Mon, Jan 12, 2009 at 8:34 PM, Magnus Hörlin wrote:
> Chris Silva wrote:
>> Hi, folks.
>>
>> My current vdr is instaled over "normal" ubuntu desktop since forever.
>> Now I want to try something similar starting with ubuntu server and
>> reducing installed packages to the minimum.
>>
>> I found
On Wed, Jan 14, 2009 at 3:41 PM, Chris Silva <2manybi...@gmail.com> wrote:
> I'm having problems compiling VDR 1.7.0 and 1.7.3.
>
> This is the error:
>
> /usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:64:28:
> error: linux/compiler.h: No such file or directory
> In file included from
On Thu, Jan 15, 2009 at 12:45 AM, user. vdr wrote:
> On Wed, Jan 14, 2009 at 3:41 PM, Chris Silva <2manybi...@gmail.com> wrote:
>> I'm having problems compiling VDR 1.7.0 and 1.7.3.
>>
>> This is the error:
>>
>> /usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:64:28:
>> error: linux/co
On Thu, Jan 15, 2009 at 2:50 AM, Chris Silva <2manybi...@gmail.com> wrote:
>
> Hi.
>
> Thanks for the help. Installing things from memory can get you into trouble.
>
> After writing the mail, read my notes and found the error...
>
> A simple
> cp /usr/src/linux-headers-$(uname -r)/include/linux/co
Hi,
at the moment I use 2 satellites (Astra1 @ 19.2E, Hotbird @ 13.0E) with 3
budget cards and cables (2x Astra from a quad LNB, 1x Hotbird from a single)
with the capabilities patch. In the future I may need to cut down the 3 to 2
cards / cables. I know I will need to replace the quad LNB by a qu
On Thursday 15 of January 2009, Chris Silva wrote:
> Hi.
>
> I'm having problems compiling VDR 1.7.0 and 1.7.3.
>
> This is the error:
>
> /usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:64:28:
> error: linux/compiler.h: No such file or directory
> In file included from
> /usr/local/src
thank you! Udo Richter
After I patched the runvdr-0.4.0-xserver-commandline.diff, the runvdr can auto
run sucessfully.
But auto runvdr can't change the OSD Language.
IF I logined the system, and press /etc/init.d/runvdr start, at this time the
vdr can change the OSD Language.
why?
15 matches
Mail list logo