[bt-devel] problem
Martin Gruner
bt-devel@crosswire.org
Wed, 8 Nov 2000 21:09:19 +0100
BTW, bt still crashes when closing a presenter.
Thank you for your patience with me!
Here's the output:
Martin@marten:~ > ldd bibletime
ldd: ./bibletime: No such file or directory
Martin@marten:~ > ldd /opt/kde/bin/bibletime
libbibletime_swordbackend.so.1 =>
/opt/kde/lib/libbibletime_swordbackend.so.1 (0x40015000)
libz.so.1 => /usr/lib/libz.so.1 (0x400fa000)
libXext.so.6 => /usr/X11/lib/libXext.so.6 (0x4010a000)
libX11.so.6 => /usr/X11/lib/libX11.so.6 (0x40117000)
libbibletime_backend.so.1 => /opt/kde/lib/libbibletime_backend.so.1
(0x401bd000)
libbibletime_frontend.so.1 => /opt/kde/lib/libbibletime_frontend.so.1
(0x401cc000)
libpthread.so.0 => /lib/libpthread.so.0 (0x4024e000)
libkfile.so.3 => /opt/kde/lib/libkfile.so.3 (0x40260000)
libksycoca.so.3 => /opt/kde/lib/libksycoca.so.3 (0x402de000)
libkio.so.3 => /opt/kde/lib/libkio.so.3 (0x40368000)
libkdesu.so.1 => /opt/kde/lib/libkdesu.so.1 (0x403fe000)
libutil.so.1 => /lib/libutil.so.1 (0x4042b000)
libkdeui.so.3 => /opt/kde/lib/libkdeui.so.3 (0x4042e000)
libkdecore.so.3 => /opt/kde/lib/libkdecore.so.3 (0x405fd000)
libdl.so.2 => /lib/libdl.so.2 (0x4071d000)
libDCOP.so.1 => /opt/kde/lib/libDCOP.so.1 (0x40721000)
libqt.so.2 => /usr/lib/qt2/lib/libqt.so.2 (0x4074f000)
libpng.so.2 => /usr/lib/libpng.so.2 (0x40e34000)
libjpeg.so.6 => /usr/lib/libjpeg.so.6 (0x40e52000)
libSM.so.6 => /usr/X11/lib/libSM.so.6 (0x40e75000)
libICE.so.6 => /usr/X11/lib/libICE.so.6 (0x40e7e000)
libm.so.6 => /lib/libm.so.6 (0x40e95000)
libc.so.6 => /lib/libc.so.6 (0x40eb2000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
libMesaGLU.so.3 => /usr/lib/libMesaGLU.so.3 (0x40fac000)
libMesaGL.so.3 => /usr/lib/libMesaGL.so.3 (0x40fc3000)
libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x410b9000)
libstdc++-libc6.1-1.so.2 => /usr/lib/libstdc++-libc6.1-1.so.2
(0x410cb000)
libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x41114000)
On Mittwoch, 8. November 2000 21:54, you wrote:
> What does "ldd bibetime" say?
> Maybe there's somewhere an old version.
>
> --Joachim
>
> > I have 2.2.0
> > Configure has no --disable-unicode or similar argument.
> > Now what to do?
> >
> > Martin
> >
> > On Mittwoch, 8. November 2000 20:49, you wrote:
> > > Hm, I do also have a normal build of Qt.
> > > For me it works.
> > > I'm using 2.2.1.
> > > --Joachim
> > >
> > > > Hi!
> > > >
> > > > maybe you should change it, because i just did a normal build like
> > > > many other people would do also. So the error would be there also.
> > > >
> > > > Martin
> > > >
> > > > On Mittwoch, 8. November 2000 17:10, you wrote:
> > > > > Hi!
> > > > >
> > > > > Probably it's a problem with the i18n and unicode support of Qt. We
> > > > > use often the (const char*) operator of QString, maybe you have
> > > > > disabled uncicode in Qt?
> > > > >
> > > > > I'm not so sure if the merge of Sword and e-sword would make us
> > > > > guving up the port. AFAIK e-swords interface is like swords, so a
> > > > > port would be useful.
> > > > >
> > > > > --Joachim
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > now I found out why sword didn't work. It works now, so it can't
> > > > > > be a reason anymore.
> > > > > > The "umlaut" problem is still here. Why could it be?
> > > > > > (I do not use the latest qt [2.2.0], i have the one before, but
> > > > > > IMO that can't be the issue)
> > > > > >
> > > > > > If e-sword and sword merge, we would'nt need to port. e-sword is
> > > > > > good enough.
> > > > > >
> > > > > > Martin