dvd::rip

->ABOUT / NEWS

->DOCUMENTATION
-TABLE OF CONTENTS
-INSTALLATION
-USING THE GUI
-CLUSTER MODE
-FAQ

->KEY FEATURES

->DOWNLOAD

->SUPPORT

->TRANSLATIONS

->MAILING LIST
-SEARCH ARCHIVE

->CHANGE LOG

->CREDITS

->TODO

->LINKS

http://www.exit1.org/


Re: [dvd::rip] Transcode & Fedora 5

Subject: Re: [dvd::rip] Transcode & Fedora 5
From: Francesco Romani <fromani@xxxxxxxxx>
Date: Fri, 23 Jun 2006 08:20:11 +0200
On Thu, 22 Jun 2006 16:34:32 -0400
Joe Smith <jes@xxxxxxxxxxx> wrote:

> > ...
> > In order to help debug, it's better to use freshrpms packages or, the
> > best option,
> > a in installation from sources; ...
> 
> I've swapped all my Livna packages for the corresponding Freshrpms 
> binaries, but no change.
> What exactly might be different for me compiling locally, compared to 
> the Freshrpms maintainers doing it? (I'm not arguing, just not eager to 
> dive in and try it "just to see if it helps").

For you? Approximatively, nothing :^)
For us trying to understand what's going on, having binaries with full debug
symbols it's just a need :)

But see Matthias Saou's other reply on this thread, it seems there are
packages with debug symbols, so everyone can be happy :)

> >> $ LD_ASSUME_KERNEL=2.4.19 dvdrip
> >> /usr/bin/perl: error while loading shared libraries: libresolv.so.2:
> >> cannot open shared object file: No such file or directory
> >> $ LD_ASSUME_KERNEL=2.4.19 transcode
> >> transcode: error while loading shared libraries: libpthread.so.0: cannot
> >> open shared object file: No such file or directory
> > That's quite strange, it should not happen
> I guess that the "LD_ASSUME_KERNEL" forces the app to load specific 
> (older) version(s) of some sensitive libraries, which I don't have.

LD_ASSUME_KERNEL select the behaviour of dynamic loader in a system with both
old-style (LinuxThreads) and new-style (NPTL) threading libraries; new-style
threads can create trouble to some applications (unfortunately, transcode is
one of this applications), so LD_ASSUME_KERNEL trick comes out.

I don't have yet a valid explanation for this behaviour; But IIRC Fedora Core
5 just no longer ships old threading libraries (LinuxThreads), but only new
ones; this can explain the behaviour that you're experiencing.
Any fedora expert can confirm/deny? :)

> Thanks!

You're welcome ;)
I'm only doing my mantainership duties =)

Best regards,

-- 
Francesco Romani - Ikitt ['people always complain, no matther what you do']
IM contact    : (email first, Antispam default deny!) icq://27-83-87-867
known bugs    : http://www.transcoding.org/cgi-bin/transcode?Bug_Showcase
tiny homepage : http://fromani.exit1.org (see IDEAS if you want send code!)

 

Archive powered by MHonArc. Search powered by ht://dig.

[ top ]