[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: libqt3 problem



On Fri, May 16, 2003 at 08:53:47PM +0200, Magnus Andersson wrote:
> Hello!
> 
> I have problems with libqt3 (probably) in debian woody. When I start an
> application called dcgui-qt (http://dc.ketelhot.de/) I get this:
> 
> /usr/bin/dcgui-qt
> Checking dclib version ...
> Using '0.2.13'
> Checking qt version ...
> Compiled for '3.0.3' using '3.0.3'
> Checking qt privates ...
> private test ok !

[snip errors]

> 
> binaries can be found here:
> deb http://80.223.193.71/debian/woody/ ./
> 
> The forum for the application (dcgui-qt) helped me with some problems
> but not this one.
> What I have tried so far.
> 
> 1. Installed debian woody from scratch on another server. dcgui-qt works
> fine.
> 2. I used a backup from problem server and imported it into a virtual
> vmware pc. problem still there so it should not be any hardware
> problems.
> 3.There are just a few packages in debian woody that depends on libqt3
> but psi (jabber client) is one. When I start psi I get a Segmentation
> fauilt.
> 4. I downloaded qt from unstable and compiled it under /usr/local/qt and
> removed libqt3, psi libqt3-mt, libdc0 and dcgui-qt. After that I
> compiled dcgui-qt and dclib. Now it works.
> 
> The problem server is far from here and I do not want to reinstall it
> because a lot of people use webmail and stuff on the server. One more
> thing if I do not use absolute path on problem server I get this:
> 
> dcgui-qt
> Checking dclib version ...
> Using '0.2.13'
> Checking qt version ...
> Compiled for '3.0.3' using '3.0.3'
> Checking qt privates ...
> private test ok !
> Signal (11) received, stackdump follows; eax='00000000', ebx='40bdecfc',

[snip some more]

> 
> A lot of addr2line messages and on my newly installed woody server it
> works without absolute path.
> 
> My PATH is: /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
> My ld.so.conf is: /usr/X11R6/lib

Run ldd on whichever libqt3.so is being used by dc-gui.  It should link
against libstdc++3, iirc.  Anything but libstdc++5, anyway :) The
version of libstdc++ it links against could well be the issue here; g++
3.2 changed the ABI for C++, so programs built with one version of g++
can only be used with libraries built with the same one.  Since packages
from Debian are h0rked, are you *sure* you didn't rebuild your libqt3
from /usr with g++ 3.2?

Anyway, my idea doesn't quite fit your symptoms, but it's the obvious
(for me, anyway) problem, so we can at least rule it out quickly enough
:)

-- 
Rob Weir <rweir@ertius.org>  |   mlspam@ertius.org   |   http://www.ertius.org/
GPG keys: 1024D/1E73B7CD, 4096R/3ABDE5EC     |      Do I look like I want a CC?
Words of the day:    digicash morse Comirex csystems airframe overthorw Serbian

Attachment: pgpWwnm7rOGBK.pgp
Description: PGP signature


Reply to: