Hi lyxers,
for the first time a new lyx release does not compile for me out of the box.
System: Debian 3.0 with official kde3.2 backports.
[EMAIL PROTECTED]:~/Software/lyx/lyx-1.3.4$ ./configure
--prefix=/usr/local/stow/lyx-1.3.4-1 --with-frontend=qt
--with-qt-dir=/usr/share/qt3
results in
Configuration
Host type: i686-pc-linux-gnu
Special build flags:
C Compiler: gcc
C Compiler flags: -g -O2
C++ Compiler: g++ (2.95.4)
C++ Compiler flags: -O -Wno-non-template-friend -ftemplate-depth-30
Linker flags:
Frontend: qt
Qt version: 3.2.1
LyX binary dir: /usr/local/stow/lyx-1.3.4-1/bin
LyX files dir: /usr/local/stow/lyx-1.3.4-1/share/lyx
Configuration of LyX was successful.
running make gives:
make[6]: Entering directory `/home/karsten/Software/lyx/lyx-1.3.4/src/frontends/qt2/ui'
/usr/share/qt3//bin/uic -tr qt_ BiblioModuleBase.ui -o BiblioModuleBase.h
/usr/share/qt3//bin/uic -tr qt_ -impl BiblioModuleBase.h BiblioModuleBase.ui -o
BiblioModuleBase.C
/usr/share/qt3//bin/uic: relocation error: /usr/lib/libkio.so.4: undefined symbol:
unregisterStaticDeleter__7KGlobalP18KStaticDeleterBase
make[6]: *** [BiblioModuleBase.C] Fehler 127
make[6]: Leaving directory `/home/karsten/Software/lyx/lyx-1.3.4/src/frontends/qt2/ui'
make[5]: *** [all-recursive] Fehler 1
make[5]: Leaving directory `/home/karsten/Software/lyx/lyx-1.3.4/src/frontends/qt2/ui'
make[4]: *** [all-recursive] Fehler 1
make[4]: Leaving directory `/home/karsten/Software/lyx/lyx-1.3.4/src/frontends/qt2'
make[3]: *** [all-recursive] Fehler 1
make[3]: Leaving directory `/home/karsten/Software/lyx/lyx-1.3.4/src/frontends'
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/home/karsten/Software/lyx/lyx-1.3.4/src'
make[1]: *** [all] Fehler 2
make[1]: Leaving directory `/home/karsten/Software/lyx/lyx-1.3.4/src'
make: *** [all-recursive] Fehler 1
[EMAIL PROTECTED]:~/Software/lyx/lyx-1.3.4$
I tried gcc-3.0/g++-3.0 as well, but then configure could not create a simple qt
binary.
As I'm short on time now I simply post these results without investigating further.
Any hints on how I can provide "better" debugging information are welcome.
Yours,
Karsten
