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@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >
