Starting vdr under suse 10.1 gave me errors like: "error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory" and "error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory". The culprit seems to be "export LD_ASSUME_KERNEL=2.4.1" before the vdr call. Without "export LD_ASSUME_KERNEL=2.4.1" vdr starts fine. Jörg
Hi, me did a bit diff vdr install under 10.1:
1. me installed via Yast Suse's own 1.3* rpm (this also installed all needed config files like runvdr) 2. i build my own 1.4.0 and overwrite the vdr bin and plugin libs (in real me made only symlinks from the VDR src dir) 3. Suse use for VDR 1.3* also config files and dirs named "vdr13" like /etc/vdr13, /usr/bin/runvdr13, /usr/bin/vdr13 and me renamed all back to "vdr" (thats not needed but i dont like this vdr13:) )
This way me didnt have your prob but maybe in Suse have already in some config this "export LD_ASSUME_KERNEL=2.4.1".
Regards Mike
PS: only prob you have this way is that Suse's own runvdr didnt like plugin lib/names with an "-" in the name so you have to remove it. (rename streamdev-server to streamdevserver)
Joerg Riechardt schrieb:
Starting vdr under suse 10.1 gave me errors like: "error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory" and "error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory". The culprit seems to be "export LD_ASSUME_KERNEL=2.4.1" before the vdr call. Without "export LD_ASSUME_KERNEL=2.4.1" vdr starts fine. Jörg
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Thursday 18 May 2006 01:49, Michael Müllner wrote:
Hi, me did a bit diff vdr install under 10.1:
- me installed via Yast Suse's own 1.3* rpm (this also installed all
needed config files like runvdr) 2. i build my own 1.4.0 and overwrite the vdr bin and plugin libs (in real me made only symlinks from the VDR src dir) 3. Suse use for VDR 1.3* also config files and dirs named "vdr13" like /etc/vdr13, /usr/bin/runvdr13, /usr/bin/vdr13 and me renamed all back to "vdr" (thats not needed but i dont like this vdr13:) )
Why on earth are you doing that? You are overwriting non-config files managed by rpm. That means your installation gets wrecked if we release e.g. a maintenance update for vdr. A distro upgrade will also overwrite your files again because vdr appears to be installed. Please either use the rpm package properly (feedback/bug reports welcome) or just don't install it at all.
PS: only prob you have this way is that Suse's own runvdr didnt like plugin lib/names with an "-" in the name so you have to remove it. (rename streamdev-server to streamdevserver)
I fixed that problem in the vdr package of the supplementary tree (Factory soon). The vdr 1.4 package is still called 'vdr13' as I had no time to check the upgrade path 1.2.6 -> 1.4 yet.
cu Ludwig
On Thu, 2006-05-18 at 01:01 +0200, Joerg Riechardt wrote:
The culprit seems to be "export LD_ASSUME_KERNEL=2.4.1" before the vdr call. Without "export LD_ASSUME_KERNEL=2.4.1" vdr starts fine.
Does Suse 10.1 use glibc-2.4? If so, support for the old linuxthreads, which was previously enabled by LD_ASSUME_KERNEL=2.4.1 has now been dropped. This is from the glibc-2.4 release notes...
* The LinuxThreads add-on, providing pthreads on Linux 2.4 kernels, is no longer supported. The new NPTL implementation requires Linux 2.6 kernels.
FWIW - this same thing applies in Fedora Core 5 as well. The NPTL code (which is your only option with the new glibc) seems to be working fine for me with VDR-1.4.0.
Jon
-
Joerg Riechardt -
Jon Burgess -
Ludwig Nussel -
Michael Müllner