Redhat 6.1 kdevelop crashes

Robert Robert
Wed Nov 24 02:42:04 GMT 1999


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




More information about the KDevelop mailing list