Redhat 6.1 kdevelop crashes

Mark Lanser mark at dd.nl
Thu Nov 25 13:34:42 GMT 1999


please remove me from your meilinglist.
Thank you.

On 24-11-99, Jim W. Bennett <bennejw at anubis.network.com> wrote:
>Robert.M.Wheat at storage.network.com, "Jr." wrote:
>> 
>> On Mon, 22 Nov 1999, you wrote:
>> 
>> > 5. To clearify, when I click 'DOC' and then click 'Qt Library' 
> kdevelop just
>> >    simply goes away. This is what I called "crashed". Maybe the 
>wrong terminology.
>> 
>> This sounds like the ongoing 'libjpeg' problem.  KDevelop crashes 
>because it is finding the wrong
>> libjpeg library.  To verify this, run KDevelop from the command 
>line of a console.  When KDevelop
>> "goes away", it should leave a message behind in the console.
>> 
>> If this is really what the problem is, then the following should 
>help you solve the problem
>> (snipped from an earlier e-mail dated Oct 16).
>> 
>> The KDE libraries want to link with libjpeg 61.  In KDevelop, when 
>looking at the QT docs, it is a
>> KDE function doing the jpeg loading.  The QT libs (1.44) want to 
>link with libjpeg 62.  I have set
>> my symbolic links named 'libjpeg.so', and 'libjpeg.so.6' to point 
>to libjpeg.so.6.0.1.  These, of
>> course, are the libs in the kde/lib directory.  I've created a 
>new symbolic link which I named
>> 'libjpeg62.so' and set to point at 'libjpeg.so.62.0.0'.  Now, when 
>a KDE app is compiled and
>> linked, if it requires libjpeg (at run time) it will use the 61 
>version (-ljpeg on the compiler
>> command line will link the app with 'libjpeg.so').  When I compile 
>a QT app that needs jpeg
>> support, I explicitly link to 'libjpeg62' (-ljpeg62 on the compiler 
>command line), which it also
>> will find at run time.  All of this can be done without re-compiling 
>anything, that is if the apps
>> in question were compiled and linked for shared (dynamically loaded) 
>libraries.
>> 
>> Bottom line, the two versions of libjpeg are incompatable and _must_ 
>be kept separate.
>> 
>> Hope this helps!
>> 
>> --
>> Robert M. Wheat, Jr.
>> belran at worldnet.ibm.net
>
>
>I wish to thank everyone that helped on fixing my problem. Would
>especially like to thank Robert M.Wheat,Jr and Anthony Tekatch for 
>thier
>special help. Anthony probably doesn't know he helped but Robert 
>listed
>the mailing date of an email that he had received his information 
>from.
>So I went to  the mailing list on the Kdevelop Web and found Anthony's
>message. Between the two message my problem came to light. Thanks 
>to
>everyone who tried to help. Every attempt was helpful, if for nothing
>else they help to show what wasn't the problem. 
>
>My poblem was simply that my libjpeg.so.62.0.0 was a '0' size file. 
>I
>did an 'rpm -Uhiv --force' to all libjpeg files (three in all) on 
>my
>Redhat 6.1 cdrom. That was all that was needed to fix the crash
>condition.
>
>There's one step that helps identify library problems.
>while in root or SU type 'ldd /usr/bin/kdevelp', which will give 
>you a
>list of the lib files it uses. The entries look like the following:
>
>libjpeg.so.6 => /usr/lib/libjpeg.so.6 90x40381000)
>
>There is just one entry off many entries. There is only one libjpeg 
>file
>listed. By the way, the entry above was my problem. What it should 
>have
>looked like and does now:
>
>libjpeg.so.62 => /usr/lib/libjpeg.so.62 90x40381000)
>
>Thanks to All;
>
>Jim
>
>
>
>





More information about the KDevelop mailing list