Re: [vdr] Compilation issues with recent DVB header files vs libc6
> According to my information (a message on the linux-dvb mailinglist), the > old mailinglists (V4L and DVB) are now merged into linux-media. what does "merged" mean? Are Posts on the "old" list replicated to the new one? Regadrs, Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Compilation issues with recent DVB header files vs libc6
Op Wo, 8 april, 2009 15:04, schreef Klaus Schmidinger: > On 04/08/09 15:00, Matthias Becker wrote: >> Hi, >> >> is the linux-dvb ML still "alive"? >> maybe http://vger.kernel.org/vger-lists.html#linux-media is read more >> frequently > > That one has way too much non DVB related traffic for me. > > Klaus According to my information (a message on the linux-dvb mailinglist), the old mailinglists (V4L and DVB) are now merged into linux-media. The V4L/DVB mailinglist are infact not used any more for patches (and a global statement was made to send those patches to the linux-media mailinglist) and I haven't seen any of the developers being active on it for some time. Full information was made in early January I believe. More information is available on the Linuxtv.org frontpage [1]. Regards, Niels Wagenaar [1] http://www.linuxtv.org/news.php?entry=2009-01-06.mchehab ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] ERROR (thread.c,225): Keine Berechtigung
On every start of the vdr I get this error message:
Apr 2 00:33:36 vdr vdr: [2462] ERROR (thread.c,225): Keine Berechtigung
It comes from cThread::SetPriority and seems to be harmless, but annoying.
Is the attached patch the right cure?
Gerald
--- vdr-1.6.0/thread.c.orig 2009-04-08 15:33:52.0 +0200
+++ vdr-1.6.0/thread.c 2009-04-08 15:34:22.0 +0200
@@ -220,7 +220,7 @@
void cThread::SetPriority(int Priority)
{
- if (setpriority(PRIO_PROCESS, 0, Priority) < 0)
+ if (setpriority(PRIO_PROCESS, getuid(), Priority) < 0)
LOG_ERROR;
}
This message was sent using IMP, the Internet Messaging Program.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Compilation issues with recent DVB header files vs libc6
On Wednesday 08 April 2009 14:04:39 Klaus Schmidinger wrote: > On 04/08/09 15:00, Matthias Becker wrote: > > Hi, > > > > is the linux-dvb ML still "alive"? > > maybe http://vger.kernel.org/vger-lists.html#linux-media is read more > > frequently > > That one has way too much non DVB related traffic for me. Agreed - and since I subbed/unsubbed I've been getting a lot more spam to my dvb address. Can't be sure it's connected, but... Andy ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Compilation issues with recent DVB header files vs libc6
On 04/08/09 15:00, Matthias Becker wrote: > Hi, > > is the linux-dvb ML still "alive"? > maybe http://vger.kernel.org/vger-lists.html#linux-media is read more > frequently That one has way too much non DVB related traffic for me. Klaus > 2009/4/8 Klaus Schmidinger : >> On 04/08/09 01:21, Tobi wrote: >>> Hi! >>> >>> Recent DVB driver releases (now in Kernel 2.6.29) cause trouble compiling >>> VDR (see snippet A below). >>> >>> The common solution to this seems to be to add a "-D__KERNEL_STRICT_NAMES". >>> >>> It felt wrong somehow and I didn't liked this, so I tried another >>> solution, which is to have any libc6 includes appear before the >>> linux DVB header includes . Doing this only in dvbdevice.c seems >>> to do the trick for VDR (see snippet B). I works for VDR 1.6.0 as well as >>> VDR 1.7.4. >>> >>> I think the root of this problem is caused by the Kernel headers / DVB >>> drivers changing from asm/types.h to linux/types.h: >>> >>> -#include >>> +#include >>> >>> How should this problem ideally be fixed? Is my solution (snippet B) >>> better than using -D__KERNEL_STRICT_NAMES or should the kernel / DVB >>> driver developers be blamed for this? >> My 2ct: >> >> - An application should not need to use -D__KERNEL_STRICT_NAMES. >> - Any header file that requires other header files to be included >> should do so by itself. >> - The sequence in which header files are included should not matter. >> I normally list them alphabetically, to easily find a particular one. >> >> I currently solve the broken DVB driver header files by replacing them >> with the ones from an earlier driver version, where they still worked. >> >> I had posted this problem on the linux-dvb ML a while ago, but apparently >> nobody cared... >> >> Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Compilation issues with recent DVB header files vs libc6
Hi, is the linux-dvb ML still "alive"? maybe http://vger.kernel.org/vger-lists.html#linux-media is read more frequently Regards, Matthias 2009/4/8 Klaus Schmidinger : > On 04/08/09 01:21, Tobi wrote: >> Hi! >> >> Recent DVB driver releases (now in Kernel 2.6.29) cause trouble compiling >> VDR (see snippet A below). >> >> The common solution to this seems to be to add a "-D__KERNEL_STRICT_NAMES". >> >> It felt wrong somehow and I didn't liked this, so I tried another >> solution, which is to have any libc6 includes appear before the >> linux DVB header includes . Doing this only in dvbdevice.c seems >> to do the trick for VDR (see snippet B). I works for VDR 1.6.0 as well as >> VDR 1.7.4. >> >> I think the root of this problem is caused by the Kernel headers / DVB >> drivers changing from asm/types.h to linux/types.h: >> >> -#include >> +#include >> >> How should this problem ideally be fixed? Is my solution (snippet B) >> better than using -D__KERNEL_STRICT_NAMES or should the kernel / DVB >> driver developers be blamed for this? > > My 2ct: > > - An application should not need to use -D__KERNEL_STRICT_NAMES. > - Any header file that requires other header files to be included > should do so by itself. > - The sequence in which header files are included should not matter. > I normally list them alphabetically, to easily find a particular one. > > I currently solve the broken DVB driver header files by replacing them > with the ones from an earlier driver version, where they still worked. > > I had posted this problem on the linux-dvb ML a while ago, but apparently > nobody cared... > > Klaus > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Compilation issues with recent DVB header files vs libc6
On 04/08/09 01:21, Tobi wrote: > Hi! > > Recent DVB driver releases (now in Kernel 2.6.29) cause trouble compiling > VDR (see snippet A below). > > The common solution to this seems to be to add a "-D__KERNEL_STRICT_NAMES". > > It felt wrong somehow and I didn't liked this, so I tried another > solution, which is to have any libc6 includes appear before the > linux DVB header includes . Doing this only in dvbdevice.c seems > to do the trick for VDR (see snippet B). I works for VDR 1.6.0 as well as > VDR 1.7.4. > > I think the root of this problem is caused by the Kernel headers / DVB > drivers changing from asm/types.h to linux/types.h: > > -#include > +#include > > How should this problem ideally be fixed? Is my solution (snippet B) > better than using -D__KERNEL_STRICT_NAMES or should the kernel / DVB > driver developers be blamed for this? My 2ct: - An application should not need to use -D__KERNEL_STRICT_NAMES. - Any header file that requires other header files to be included should do so by itself. - The sequence in which header files are included should not matter. I normally list them alphabetically, to easily find a particular one. I currently solve the broken DVB driver header files by replacing them with the ones from an earlier driver version, where they still worked. I had posted this problem on the linux-dvb ML a while ago, but apparently nobody cared... Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Compilation issues with recent DVB header files vs libc6
Tony Houghton wrote: > I used -D__KERNEL_STRICT_NAMES but compilation then failed on the use of > __u8 in . ISTR reading that might only be a problem > for 64-bit. I didn't had this problem. VDR 1.6.0 and 1.7.4 compile fine with 2.6.29 and GCC 4.3 on x86_64. It works also with the latest drivers from Igors repository. Tobias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
