Re: Compiling KDE apps
El Miércoles, 16 de Abril de 2003 16:37, José Manuel Pérez escribió: > Sorry, it was my mistake ... cut + copy + paste + ... and finally bad > done. Sorry, I primise not to do it again Never mind, is only that a lot of people don't know it, and it's a good idea to say it sometimes :-). > > QList is obsolete, replace QList by QPtrList, and by > > > > Ok, but I'm compiling someone else'e application, and by now it compiles > using libqt3-compat-headers Sorry, I forgot that not everyone is coding :-). I wrote that, because many people start a project with kdevelop, and have this same problem, and, I think that if you start a new program, better not to use obsolette classes. Agur ;-) -- Alex (a.k.a. suy) - GPG ID: AA8D2A01 http://lacurva.net/
Re: Compiling KDE apps
El mié, 16 de 04 de 2003 a las 12:06, Alex escribió: > El Miércoles, 16 de Abril de 2003 11:30, José Manuel Pérez escribió: > > In-Reply-To: <[EMAIL PROTECTED]> > > References: <[EMAIL PROTECTED]> > > <[EMAIL PROTECTED]> > > First off all, those headers, appear because you used "reply to", instead of > writing a new email. Do you know what threads are? That ones who use kmail > ordering messages by thread, become crazy every time you use that feature, so > _please_ don't reply to a message, to answer a new question. Send a _new_ > email to [EMAIL PROTECTED] :-) (mail archives use also threads, so > I thing is a great idea doing that ;-) ). Sorry, it was my mistake ... cut + copy + paste + ... and finally bad done. Sorry, I primise not to do it again. > > > I've got problems compiling some KDE apps. It says there is no qlist.h > > in my include path, and indeed there it is not. There is qlistview.h and > > qlistbox.h > > QList is obsolete, replace QList by QPtrList, and by . Ok, but I'm compiling someone else'e application, and by now it compiles using libqt3-compat-headers. > > Best regards. > -- > Alex (a.k.a. suy) - GPG ID: AA8D2A01 > http://lacurva.net/ Thanks to all your comments (I've received a lot of usefull responses). Regards, -- --+--- José Manuel Pérez Fuente | Universidad del País Vasco Punto Neutro EuskoNIX (UPV/EHU) | E-mail: [EMAIL PROTECTED] Plaza Elhuyar, 1 (Edif. Barriola) | Tel.: +34 943 018 281 20018 San Sebastián (SPAIN) | Fax.: +34 943 219 306 --+--- signature.asc Description: PGP signature
Re: Compiling KDE apps
Am Mittwoch, 16. April 2003 11:30 schrieb José Manuel Pérez: > Hi all. > > I've got problems compiling some KDE apps. It says there is no > qlist.h in my include path, and indeed there it is not. There is > qlistview.h and qlistbox.h. > > I have kde 3.1.1 with qt 3.1.1 and followin dev packages: > libqt3-mt-dev and qt3-dev-tools. > > Someone knows what is happening. You need libqt3-compat-headers. so long, Marco
Re: Compiling KDE apps
A Dimecres 16 Abril 2003 11:30, José Manuel Pérez va escriure: > Hi all. > > I've got problems compiling some KDE apps. It says there is no qlist.h > in my include path, and indeed there it is not. There is qlistview.h and > qlistbox.h. > > I have kde 3.1.1 with qt 3.1.1 and followin dev packages: libqt3-mt-dev > and qt3-dev-tools. > > Someone knows what is happening. > > Regards, Hi, (kaixo! ) you need: libqt3-compat-headers [EMAIL PROTECTED]:~/tmp/xmlparser$ dpkg -S /usr/include/qt3/qlist.h libqt3-compat-headers: /usr/include/qt3/qlist.h [EMAIL PROTECTED]:~/tmp/xmlparser$ That's all. regards, Leo (Abur)
Re: Compiling KDE apps
El Miércoles, 16 de Abril de 2003 11:30, José Manuel Pérez escribió: > In-Reply-To: <[EMAIL PROTECTED]> > References: <[EMAIL PROTECTED]> > <[EMAIL PROTECTED]> First off all, those headers, appear because you used "reply to", instead of writing a new email. Do you know what threads are? That ones who use kmail ordering messages by thread, become crazy every time you use that feature, so _please_ don't reply to a message, to answer a new question. Send a _new_ email to [EMAIL PROTECTED] :-) (mail archives use also threads, so I thing is a great idea doing that ;-) ). > I've got problems compiling some KDE apps. It says there is no qlist.h > in my include path, and indeed there it is not. There is qlistview.h and > qlistbox.h QList is obsolete, replace QList by QPtrList, and by . Best regards. -- Alex (a.k.a. suy) - GPG ID: AA8D2A01 http://lacurva.net/
Re: Compiling KDE apps
On Wednesday 16 April 2003 11:30, José Manuel Pérez wrote: > Hi all. > > I've got problems compiling some KDE apps. It says there is no qlist.h > in my include path, and indeed there it is not. There is qlistview.h and > qlistbox.h. > > I have kde 3.1.1 with qt 3.1.1 and followin dev packages: libqt3-mt-dev > and qt3-dev-tools. try 'apt-get install libqt3-headers' and you will be happy. > Someone knows what is happening. > > Regards, Sebastian
Re: Compiling KDE apps
> I've got problems compiling some KDE apps. It says there is no qlist.h > in my include path, and indeed there it is not. There is qlistview.h and > qlistbox.h. apt-get install libqt3-compat-headers. b. :)
Compiling KDE apps
Hi all. I've got problems compiling some KDE apps. It says there is no qlist.h in my include path, and indeed there it is not. There is qlistview.h and qlistbox.h. I have kde 3.1.1 with qt 3.1.1 and followin dev packages: libqt3-mt-dev and qt3-dev-tools. Someone knows what is happening. Regards, -- --+--- José Manuel Pérez Fuente | Universidad del País Vasco Punto Neutro EuskoNIX (UPV/EHU) | E-mail: [EMAIL PROTECTED] Plaza Elhuyar, 1 (Edif. Barriola) | Tel.: +34 943 018 281 20018 San Sebastián (SPAIN) | Fax.: +34 943 219 306 --+--- signature.asc Description: PGP signature
Re: compiling KDE apps
Frank Van Damme wrote: Hi list, Every now and then I meet a good app that isn't in Debian (sid) and compile it myself. It doesn't always seem so simple wth kde apps however. I tried to compile kopete; Compiling goes fine but when I run the program (from the source dir,) the prompt comes back immediately, and there's no kopete window. This is in my proces list: yalu 621 0.0 5.9 25248 15300 ? S12:04 0:00 kopete -session 117f01000 When I run from /usr/local/stow/kopete, where I installed it, this is what I get: kopete: KopeteEmoticons::initEmoticons : WARNING: emoticon-map not found It didn't seem to want to be installed anywhere other than /usr. I ended up taring up an install of it and running alien. I guess either kde or kopete doesn't know enough to look in both /usr and /usr/local for shared files. (like perl, python, emacs, tex, etc.) Keep your eye on kopete. I like the idea of a dockable IM application, but I've had nothing but bad luck with it. It has, on many occasions, eaten all of my disk space (with a 800+MB .xsession-errors file) and eaten all my memory. In the end, I gave up and went back to gaim. Steve Dunham [EMAIL PROTECTED] http://www.cse.msu.edu/~dunham
compiling KDE apps
Hi list, Every now and then I meet a good app that isn't in Debian (sid) and compile it myself. It doesn't always seem so simple wth kde apps however. I tried to compile kopete; Compiling goes fine but when I run the program (from the source dir,) the prompt comes back immediately, and there's no kopete window. This is in my proces list: yalu 621 0.0 5.9 25248 15300 ? S12:04 0:00 kopete -session 117f01000 When I run from /usr/local/stow/kopete, where I installed it, this is what I get: kopete: KopeteEmoticons::initEmoticons : WARNING: emoticon-map not found Anyone? -- Frank Van Damme| "Saying 8MB of RAM doesn't do as much anymore is http://www.| like saying a gallon of water holds more than it openstandaarden.be | did in 1988."--George Adkins
Re: Bug in libqt3 3.1.2? Was: Compiling KDE apps: Still not clear...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 March 2003 12:00, Marc Schiffbauer wrote: > * Ralf Nolden schrieb am 18.03.03 um 08:57 Uhr: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On Tuesday 18 March 2003 01:18, Erik Johansson wrote: > > > On Tuesday 18 March 2003 00.10, Ben Burton wrote: > > > > > OMG, you're right! I've just copied /usr/lib/libqt.so.3.1.1 to > > > > > /usr/share/qt3 named as libqt.so and libqt3.so and voila - it all > > > > > works! > > > > > > It seems to be a bug in libqt3 version 3.1.2 (libqt3-mt and > > > libqt3-mt-dev). The symlinks (libqt-mt.so*) in /usr/share/qt3/lib > > > points to > > > libqt-mt.so.3.1.1 not 3.1.2. > > > > ARGL. Thanks for notifying. I guess that got slipped through after I > > changed from 3.1.1 to 3.1.2. Too stupid that Qt requires so much manual > > work :-( > > > > I'll rebuild Qt and upload but I want to keep the same version number. > > > > Ralf > > So that nobody (or no apt-get) notices the update? Would that really > make sense? Yes, you only need to reinstall libqt3-mt-dev. Ralf > > -Marc > > -- > +-O . . . o . . . O . . . o . . . O . . . ___ . . . O . . . o .-+ > > | Ein neuer Service von Links2Linux.de: / o\ RPMs for SuSE | > | --> PackMan! <-- naeheres unter| __| and others| > | http://packman.links2linux.de/ . . . O \__\ . . . O . . . O . | - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+dw4xu0nKi+w1Ky8RAjc5AJ9QBmniLdxfL6SCnPXe3CaAQp3vNQCfbMGV PUXD0kM9mZDDT0ZLcWQ/+Sk= =bgq2 -END PGP SIGNATURE-
Re: Bug in libqt3 3.1.2? Was: Compiling KDE apps: Still not clear...
* Ralf Nolden schrieb am 18.03.03 um 08:57 Uhr: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tuesday 18 March 2003 01:18, Erik Johansson wrote: > > On Tuesday 18 March 2003 00.10, Ben Burton wrote: > > > > OMG, you're right! I've just copied /usr/lib/libqt.so.3.1.1 to > > > > /usr/share/qt3 named as libqt.so and libqt3.so and voila - it all > > > > works! > > > > It seems to be a bug in libqt3 version 3.1.2 (libqt3-mt and libqt3-mt-dev). > > The symlinks (libqt-mt.so*) in /usr/share/qt3/lib points to > > libqt-mt.so.3.1.1 not 3.1.2. > > ARGL. Thanks for notifying. I guess that got slipped through after I changed > from 3.1.1 to 3.1.2. Too stupid that Qt requires so much manual work :-( > > I'll rebuild Qt and upload but I want to keep the same version number. > > Ralf So that nobody (or no apt-get) notices the update? Would that really make sense? -Marc -- +-O . . . o . . . O . . . o . . . O . . . ___ . . . O . . . o .-+ | Ein neuer Service von Links2Linux.de: / o\ RPMs for SuSE | | --> PackMan! <-- naeheres unter| __| and others| | http://packman.links2linux.de/ . . . O \__\ . . . O . . . O . |
Re: Compiling KDE Apps (new thread)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 March 2003 04:56, Bruce wrote: > There have been a number of conflicting suggestions about problems with > compiling KDE apps, and I suspect the various suggestions/thoughts may be > right for different configurations. However, as it now stands, it is not > clear what the problem many people seem to be having, or what the solution > is. Some say "there's a bug", the packagers say "no, there's not". > > I have read /usr/share/doc/libqt3-mt/README-Debian.gz, and tried the > various suggestions there, but the problem doesn't seem to be addressed. > However, I am not a coder, and really know nothing about how compiling > programs work, so probably wouldn't know the solution if I read it > somewhere. > > I also want to say that this is (for me, in any case) not a big issue; the > KDE debs made available by Ralf are fabulous, work great, and have made a > big difference for anyone wanting to run KDE on a stable machine. If I > can't compile the one or two programs not available through ktown.kde.org, > I don't really care. So, rather than griping, I figure the least I can do > is try to digest some of the information on the list to help sort out what > appears to be a fairly common problem. If you want to compile a KDE app, you're best off debianizing it: dh_make -t /usr/share/doc/kdelibs4-dev/dh-make The problem you found with the wrong symlinks in qt-3.1.2 packages is correct. I'm rebuilding Qt to address this problem. Martin: It may be best if we put all symlinks from /usr/lib to /usr/share/qt3/lib in the -dev.links files instead of spreading them around. They really only do make sense in the dev packages anyway and they need updating for each updated Qt build when the library version number changes. Putting them all in the -dev packages may be the best solution IMHO so we don't forget any of the changes that have to be made (that would reduce the changes to libqt3-dev.links and libqt3-mt-dev.links) Ralf > > Here's what I can gather to date: > > First, I am still not sure which QT development packages need to be > installed to compile KDE3 applications. There are two, mutually exclusive > packages - libqt3-mt-dev, and libqt3-dev. They conflict, and installing > either one will remove the other. The description for libqt3-dev says it > is deprecated in favour of libqt3-mt-dev; to quote: > > WARNING: The nonthreaded version of Qt3 is > considered deprecated and may disappear anytime > in the future. Please use libqt3-mt instead > > I assume this means: > > Install libqt3-mt-dev instead of libqt3-dev > > Second, when I (and several others) install the current 3.1.2 version of > the libqt3-mt-dev package (libqt3-mt-dev_3.1.2-0woody1_i386.deb), it > creates the following symlinks in /usr/share/qt3/lib: > > libqt-mt.so --> ../../../lib/libqt-mt.so.3.1.1 > libqt-mt.so.3--> ../../../lib/libqt-mt.so.3.1.1 > libqt-mt.so.3.1 --> ../../../lib/libqt-mt.so.3.1.1 > libqt.so.3 --> ../../../lib/libqt.so.3.1.1 > libqt.so.3.1 --> ../../../lib/libqt.so.3.1.1 > > These all point to /usr/lib. However, there is no *.so.3.1.1 in /usr/lib; > the file names there are *.so.3.1.2. This would explain why people who > experience the above behaviour cannot compile anything, as configure > cannot find the qt development libraries. > > Changing the symlinks to point to ../../../lib/libqt.so.3.1.2 seems to > work for most people (though it doesn't for me, I expect there is > something else wrong with my system). So the next question is: > > Is there a bug in libqt3-mt-dev, in that the symlinks in > /usr/share/qt3/lib point to the wrong place?? > > Bruce - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+dtURu0nKi+w1Ky8RAvqtAJ933IfQxTMPKnv8HhMB3KAT7M4njwCdFiHM ncrVD7AhiPsZYIBcXRqfxys= =0cEj -END PGP SIGNATURE-
Re: Bug in libqt3 3.1.2? Was: Compiling KDE apps: Still not clear...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 March 2003 01:18, Erik Johansson wrote: > On Tuesday 18 March 2003 00.10, Ben Burton wrote: > > > OMG, you're right! I've just copied /usr/lib/libqt.so.3.1.1 to > > > /usr/share/qt3 named as libqt.so and libqt3.so and voila - it all > > > works! > > It seems to be a bug in libqt3 version 3.1.2 (libqt3-mt and libqt3-mt-dev). > The symlinks (libqt-mt.so*) in /usr/share/qt3/lib points to > libqt-mt.so.3.1.1 not 3.1.2. ARGL. Thanks for notifying. I guess that got slipped through after I changed from 3.1.1 to 3.1.2. Too stupid that Qt requires so much manual work :-( I'll rebuild Qt and upload but I want to keep the same version number. Ralf > > > The libqt.so link is provided by package libqt3-dev, which is different > > from libqt3-mt-dev (which is the Qt development package dragged in with > > kdelibs4-dev amongst other things). > > Correct me if I'm wrong, but isn't libqt3-mt-dev the correct dev pkg to use > when using libqt3-mt? It works for me, if it wasn't for the symlinks in > /usr/share/qt3/lib pointing to the wrong release. > > // Erik > > -- > Don't worry, tomorrow won't be a better day ! > > Erik Johansson <[EMAIL PROTECTED]> - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+dtF4u0nKi+w1Ky8RAvaBAJ0SiedasXJp0lBaDQcLGxGwOG8hJACfZUZt xKnC8hZdWN6pFiyDpZmtE0I= =qlOw -END PGP SIGNATURE-
Re: Compiling KDE apps: Still not clear...
On Mon, 2003-03-17 at 23:10, Ben Burton wrote: > > OMG, you're right! I've just copied /usr/lib/libqt.so.3.1.1 to > > /usr/share/qt3 named as libqt.so and libqt3.so and voila - it all works! > > The libqt.so link is provided by package libqt3-dev, which is different > from libqt3-mt-dev (which is the Qt development package dragged in with > kdelibs4-dev amongst other things). > > It might be worth making sure you have this package installed (instead > of using this manual copying of files). You cannot install libqt3-dev as well as kdelibs4-dev. Apt won't allow you. That is why I was having all the trouble in the first place. I still have a libqt.so.3 in /usr/lib (which is distinct from /usr/lib/libqt-mt.so.3), but there wasn't any links to it from /usr/share/qt3 and so wasn't being found. A
Compiling KDE Apps (new thread)
There have been a number of conflicting suggestions about problems with compiling KDE apps, and I suspect the various suggestions/thoughts may be right for different configurations. However, as it now stands, it is not clear what the problem many people seem to be having, or what the solution is. Some say "there's a bug", the packagers say "no, there's not". I have read /usr/share/doc/libqt3-mt/README-Debian.gz, and tried the various suggestions there, but the problem doesn't seem to be addressed. However, I am not a coder, and really know nothing about how compiling programs work, so probably wouldn't know the solution if I read it somewhere. I also want to say that this is (for me, in any case) not a big issue; the KDE debs made available by Ralf are fabulous, work great, and have made a big difference for anyone wanting to run KDE on a stable machine. If I can't compile the one or two programs not available through ktown.kde.org, I don't really care. So, rather than griping, I figure the least I can do is try to digest some of the information on the list to help sort out what appears to be a fairly common problem. Here's what I can gather to date: First, I am still not sure which QT development packages need to be installed to compile KDE3 applications. There are two, mutually exclusive packages - libqt3-mt-dev, and libqt3-dev. They conflict, and installing either one will remove the other. The description for libqt3-dev says it is deprecated in favour of libqt3-mt-dev; to quote: WARNING: The nonthreaded version of Qt3 is considered deprecated and may disappear anytime in the future. Please use libqt3-mt instead I assume this means: Install libqt3-mt-dev instead of libqt3-dev Second, when I (and several others) install the current 3.1.2 version of the libqt3-mt-dev package (libqt3-mt-dev_3.1.2-0woody1_i386.deb), it creates the following symlinks in /usr/share/qt3/lib: libqt-mt.so--> ../../../lib/libqt-mt.so.3.1.1 libqt-mt.so.3 --> ../../../lib/libqt-mt.so.3.1.1 libqt-mt.so.3.1--> ../../../lib/libqt-mt.so.3.1.1 libqt.so.3 --> ../../../lib/libqt.so.3.1.1 libqt.so.3.1 --> ../../../lib/libqt.so.3.1.1 These all point to /usr/lib. However, there is no *.so.3.1.1 in /usr/lib; the file names there are *.so.3.1.2. This would explain why people who experience the above behaviour cannot compile anything, as configure cannot find the qt development libraries. Changing the symlinks to point to ../../../lib/libqt.so.3.1.2 seems to work for most people (though it doesn't for me, I expect there is something else wrong with my system). So the next question is: Is there a bug in libqt3-mt-dev, in that the symlinks in /usr/share/qt3/lib point to the wrong place?? Bruce
Re: Bug in libqt3 3.1.2? Was: Compiling KDE apps: Still not clear...
> Correct me if I'm wrong, but isn't libqt3-mt-dev the correct dev pkg to use > when using libqt3-mt? It works for me, if it wasn't for the symlinks in > /usr/share/qt3/lib pointing to the wrong release. No, you're correct. But if it's looking for libqt.so then you're not using libqt3-mt, you're just using the single-threaded libqt3. Perhaps I'm misunderstanding the problem? b.
Re: Compiling KDE apps: Still not clear...
On Tuesday 18 March 2003 00:10, Ben Burton wrote:
> > OMG, you're right! I've just copied /usr/lib/libqt.so.3.1.1 to
> > /usr/share/qt3 named as libqt.so and libqt3.so and voila - it all
> > works!
>
> The libqt.so link is provided by package libqt3-dev, which is
> different from libqt3-mt-dev (which is the Qt development package
> dragged in with kdelibs4-dev amongst other things).
>
> It might be worth making sure you have this package installed
> (instead of using this manual copying of files).
I think it would be even better not to build KDE tarballs manually.
Roughly debianizing them seems to be a lot less troublesome.
I'm using an adapted template debian/rules file (see below) with dh_make
$ dh_make --templates /home/michael/projects/packaging/dh_make_kde
$ debuild -us -uc -b
The resulting package is far from pretty and lintian complains loudly.
But, what can I say, in most cases it works surprisingly well. Also,
it's a good idea to have a current version of admin/debianrules handy
as this file is outdated in several ("third party") KDE application
tarballs.
Michael
#!/usr/bin/make -f
# Sample debian/rules that uses debhelper.
# GNU copyright 1997 to 1999 by Joey Hess.
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
# This is the debhelper compatibility version to use.
export DH_COMPAT=3
DH_ALWAYS_EXCLUDE=CVS
-include debian/debiandirs
debian/debiandirs: admin/debianrules
perl -w admin/debianrules echodirs > debian/debiandirs
#DPKG_ARCH#
config.status: configure
dh_testdir
# Add here commands to configure the package.
./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE)
$(configkde)
build: build-stamp
build-stamp: config.status
dh_testdir
# Add here commands to compile the package.
$(MAKE)
#/usr/bin/docbook-to-man debian/#PACKAGE#.sgml > #PACKAGE#.1
touch build-stamp
clean:
dh_testdir
dh_testroot
rm -f build-stamp
# Add here commands to clean up after the build process.
-#CLEAN#
dh_clean debian/debiandirs
debian-clean:
dh_testdir
-rm -f build-stamp
if test -d CVS; then \
make -f admin/Makefile.common cvs-clean ;\
fi
-make distclean
install: build
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs
# Add here commands to install the package into debian/#PACKAGE#.
$(MAKE) install DESTDIR=$(CURDIR)/debian/#PACKAGE#
# Build architecture-independent files here.
binary-indep: build install
# We have nothing to do by default.
# Build architecture-dependent files here.
binary-arch: build install
dh_testdir
dh_testroot
# dh_installdebconf
dh_installdocs
dh_installmenu
dh_undocumented #PACKAGE#.1
dh_installchangelogs #CHANGELOGS#
dh_link
dh_strip
dh_compress --exclude=.docbook --exclude=.bz2
dh_fixperms
dh_makeshlibs
dh_installdeb
dh_shlibdeps
dh_gencontrol
dh_md5sums
dh_builddeb
binary: binary-indep binary-arch
.PHONY: build clean binary-indep binary-arch binary install
--
Michael SchuerigAll good people read good books
mailto:[EMAIL PROTECTED] Now your conscience is clear
http://www.schuerig.de/michael/ --Tanita Tikaram, "Twist In My Sobriety"
Bug in libqt3 3.1.2? Was: Compiling KDE apps: Still not clear...
On Tuesday 18 March 2003 00.10, Ben Burton wrote: > > OMG, you're right! I've just copied /usr/lib/libqt.so.3.1.1 to > > /usr/share/qt3 named as libqt.so and libqt3.so and voila - it all works! It seems to be a bug in libqt3 version 3.1.2 (libqt3-mt and libqt3-mt-dev). The symlinks (libqt-mt.so*) in /usr/share/qt3/lib points to libqt-mt.so.3.1.1 not 3.1.2. > The libqt.so link is provided by package libqt3-dev, which is different > from libqt3-mt-dev (which is the Qt development package dragged in with > kdelibs4-dev amongst other things). Correct me if I'm wrong, but isn't libqt3-mt-dev the correct dev pkg to use when using libqt3-mt? It works for me, if it wasn't for the symlinks in /usr/share/qt3/lib pointing to the wrong release. // Erik -- Don't worry, tomorrow won't be a better day ! Erik Johansson <[EMAIL PROTECTED]>
Re: Compiling KDE apps: Still not clear...
> OMG, you're right! I've just copied /usr/lib/libqt.so.3.1.1 to > /usr/share/qt3 named as libqt.so and libqt3.so and voila - it all works! The libqt.so link is provided by package libqt3-dev, which is different from libqt3-mt-dev (which is the Qt development package dragged in with kdelibs4-dev amongst other things). It might be worth making sure you have this package installed (instead of using this manual copying of files). b.
Re: Compiling KDE apps: Still not clear...
On Mon, 2003-03-17 at 16:31, Hendrik Sattler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am Montag, 17. März 2003 16:02 schrieb Andrew Ingram: > > ldconfig -p reports: > > libqt.so.3.1 (libc6) => /usr/lib/libqt.so.3.1 > > libqt.so.3 (libc6) => /usr/lib/libqt.so.3 > > > > and both /usr/lib/libqt.so.3.1 & /usr/lib/libqt.so.3 are symbolic links > > to /usr/lib/libqt.so.3.1.1 > > > > So the links all seem true, and ldconfig knows about the library and > > it's path, but for some reason, the linker still returns cannot find > > -lqt! > > > > I've had this problem for a very long time now :-( > > Do you have a libqt3.so (no other suffix appended)? The linker can only find > this .so and .a files. Whatever ldconfig finds is important to ldso but not > to the linker. OMG, you're right! I've just copied /usr/lib/libqt.so.3.1.1 to /usr/share/qt3 named as libqt.so and libqt3.so and voila - it all works! This is great. Thank you very much. I'm off to compile some apps that I've been wanting for a very long time :-) Andy
Re: Compiling KDE apps: Still not clear...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 17. März 2003 16:02 schrieb Andrew Ingram: > ldconfig -p reports: > libqt.so.3.1 (libc6) => /usr/lib/libqt.so.3.1 > libqt.so.3 (libc6) => /usr/lib/libqt.so.3 > > and both /usr/lib/libqt.so.3.1 & /usr/lib/libqt.so.3 are symbolic links > to /usr/lib/libqt.so.3.1.1 > > So the links all seem true, and ldconfig knows about the library and > it's path, but for some reason, the linker still returns cannot find > -lqt! > > I've had this problem for a very long time now :-( Do you have a libqt3.so (no other suffix appended)? The linker can only find this .so and .a files. Whatever ldconfig finds is important to ldso but not to the linker. HS - -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+dfhWzvr6q9zCwcERAnRNAKCQmVQVlCrM/BdDslAw61ij5l/0FQCeNMvy S+4DajcpghIUSR2WxiAlho8= =zGPp -END PGP SIGNATURE-
Re: Compiling KDE apps: Still not clear...
måndagen den 17 mars 2003 16.02 skrev Andrew Ingram: > ./configure --prefix=/usr --with-qt-dir=/usr/share/qt3 > > checking for Qt... configure: error: Qt (>= Qt 2.2.2) (libraries) not > found. Please check your installation! > So the links all seem true, and ldconfig knows about the library and > it's path, but for some reason, the linker still returns cannot find > -lqt! > > I've had this problem for a very long time now :-( Aren't the packages tested before they enter SID. I thought that was the whole purpose of all the delays, the very careful testing Anyway, I have no problem with a simple --with-qt-includes=/usr/include/qt (I am using my own new packages, but that should make a difference here) Karolina
Re: Compiling KDE apps: Still not clear...
On Mon, 2003-03-17 at 14:12, Bruce wrote: > > >> > >> I get the above error whether I run > >>./configure > >> or > >>./configure --prefix=/usr --with-qt-includes=/usr/include/qt3 > >> or > >>./configure --prefix=/usr --with-qt-includes=/usr/include/qt3 > >> --with-qt-libraries=/usr/share/qt3/lib > > > > Try ./configure --prefix=/usr --with-qt-dir=/usr/share/qt3 > > > > I had tried that as well, no difference. Still get the > > checking for Qt... configure: error: Qt (>= Qt 3.0.2) (library qt-mt) not > found. > > error. This happens while attempting to compile any KDE apps. > > Everything else seems to work very well. The only other problem I have > notices is that the audiocd:/ kioslave returns an error, even though > kdemultimedia-kio-plugins is installed (assuming this replaces the former > kio-audiocd plugin), but I can't see how that would be related. Me too! I get: ./configure --prefix=/usr --with-qt-dir=/usr/share/qt3 checking for Qt... configure: error: Qt (>= Qt 2.2.2) (libraries) not found. Please check your installation! In config.log, the output from the linker is: c++ -o conftest -O2 -fno-exceptions -fno-check-new -I/usr/share/qt3/include -I/usr/X11R6/include -L/usr/share/qt3/lib -L/usr/X11R6/lib conftest.C -lqt -lpng -lz -lm -ljpeg -lXext -lX11 -lSM -lICE -lresolv 1>&5 /usr/bin/ld: cannot find -lqt collect2: ld returned 1 exit status As you can see, it's libpath looks in /usr/share/qt3/lib and it tries to include -lqt (which must equate to libqt.so.whatever). Inside /usr/share/qt3/lib, I have a libqt.so.3 and a libqt.so.3.1 which are both symbolic links to /usr/lib/libqt.so.3.1.1 libqt.so.3.1.1 is a shared library file around 6MB in size. ldconfig -p reports: libqt.so.3.1 (libc6) => /usr/lib/libqt.so.3.1 libqt.so.3 (libc6) => /usr/lib/libqt.so.3 and both /usr/lib/libqt.so.3.1 & /usr/lib/libqt.so.3 are symbolic links to /usr/lib/libqt.so.3.1.1 So the links all seem true, and ldconfig knows about the library and it's path, but for some reason, the linker still returns cannot find -lqt! I've had this problem for a very long time now :-(
Re: Compiling KDE apps: Still not clear...
>> >> I get the above error whether I run >> ./configure >> or >> ./configure --prefix=/usr --with-qt-includes=/usr/include/qt3 >> or >> ./configure --prefix=/usr --with-qt-includes=/usr/include/qt3 >> --with-qt-libraries=/usr/share/qt3/lib > > Try ./configure --prefix=/usr --with-qt-dir=/usr/share/qt3 > I had tried that as well, no difference. Still get the checking for Qt... configure: error: Qt (>= Qt 3.0.2) (library qt-mt) not found. error. This happens while attempting to compile any KDE apps. Everything else seems to work very well. The only other problem I have notices is that the audiocd:/ kioslave returns an error, even though kdemultimedia-kio-plugins is installed (assuming this replaces the former kio-audiocd plugin), but I can't see how that would be related. Bruce
Re: Compiling KDE apps: Still not clear...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 16 March 2003 21:40, Bruce wrote:
> ... on what I need to install. I am running KDE 3.1.1 from Ralf's Woody
> packages, on a primarily Woody system, with some packages from Sid.
>
> I have read through the various posts this month, and have tried to follow
> the advice given, but still can't manage to get past this configure error:
>
> checking for Qt... configure: error: Qt (>= Qt 3.0.2) (library qt-mt) not
> found. Please
> check your installation!
> For more details about this problem, look at the end of config.log.
> Make sure that you have compiled Qt with thread support!
>
> (The details from config.log are set out below)
>
> I do have the following packages installed, from Ralf's repository:
>
> libqt3-compat-headers
> libqt3-headers
> libqt3-mt-dev
> libqt3-plugins-headers
> qt3-apps-dev
> kdebase-dev
> kdelibs4-dev
> kdemultimedia-dev
> kdegraphics-dev
>
> (I didn't install libqt3-dev, because it conflicts with some of the above;
> I installed the above packages as they were the packages suggested on this
> list. What is libqt3-dev for??)
>
> I get the above error whether I run
> ./configure
> or
> ./configure --prefix=/usr --with-qt-includes=/usr/include/qt3
> or
> ./configure --prefix=/usr --with-qt-includes=/usr/include/qt3
> --with-qt-libraries=/usr/share/qt3/lib
Try ./configure --prefix=/usr --with-qt-dir=/usr/share/qt3
>
> I also tried running
> export QTDIR=/usr/share/qt3
> first, but I still got the same message indicated above.
>
> For the record, the program I am trying to install is kcdlabel
> v.2.11-KDE3. The relevant excerpt from config.log is:
>
> configure:21511: checking for Qt
> configure: 21578: /usr/include/qt3/qstyle.h
> taking that
> configure:21688: rm -rf SunWS_cache; g++ -o conftest -Wnon-virtual-dtor
> -Wno-long-long -Wbad-function-cast -Wundef -Wall -pedantic -W
> -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -O2
> -fno-exceptions -fno-check-new -I/usr/include/qt3 -I/usr/X11R6/include
> -DQT_THREAD_SUPPORT -D_REENTRANT -L/usr/share/qt3/lib -L/usr/X11R6/lib
> conftest.cc -lqt-mt -lpng -lz -lm -ljpeg -ldl -lXext -lX11 -lSM -lICE
> -lresolv -lpthread 1>&5
>
> /tmp/cc8TDEIj.o(.text+0xe): In function `main':
> : undefined reference to `QString::null'
>
> /tmp/cc8TDEIj.o(.text+0x13): In function `main':
> : undefined reference to `QStyleFactory::create(QString const&)'
>
> /tmp/cc8TDEIj.o(.text+0x20): In function `main':
> : undefined reference to `QCursor::QCursor[in-charge](int)'
>
> /tmp/cc8TDEIj.o(.text+0x28): In function `main':
> : undefined reference to `QCursor::~QCursor [in-charge]()'
>
> collect2: ld returned 1 exit status
> configure:21691: $? = 1
> configure: failed program was:
> #include "confdefs.h"
> #include
> #include
> #include
> #include
> #include
> #if ! (QT_VERSION >= 303)
> #error 1
> #endif
>
> int main() {
> (void)QStyleFactory::create(QString::null);
> QCursor c(Qt::WhatsThisCursor);
> return 0;
> }
> configure:21731: error: Qt (>= Qt 3.0.3) (library qt-mt) not found. Please
> check your installation!
> For more details about this problem, look at the end of config.log.
> Make sure that you have compiled Qt with thread support!
>
> Bruce
- --
We're not a company, we just produce better code at less costs.
-
Ralf Nolden
[EMAIL PROTECTED]
The K Desktop Environment The KDevelop Project
http://www.kde.org http://www.kdevelop.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+dX7mu0nKi+w1Ky8RAhFTAKCbs5cwkQFVhzX/VpgXbfDERmbV+QCeJRMs
MsUA4VGp3EPQF5ltMn7X/4c=
=B+zg
-END PGP SIGNATURE-
Re: Compiling KDE apps: Still not clear...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 17 March 2003 02:49, Chris Cheney wrote: > On Sun, Mar 16, 2003 at 08:19:52PM -0500, Bruce wrote: > > I purged and reinstalled all qt/kde -dev packages (the 3.1.2 versions > > from ktown.kde.org), but same result. > > > > Is this right? Or does this indicate something else is messed up on my > > system? > > Sounds like the ktown qt debs are messed up. they aren't :-) Ralf > > Chris - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+dYBwu0nKi+w1Ky8RAgO+AJ9Il5VaWBVpz6SlxvFRaT74Lij3VgCcCuMO BQDMO30+Z8L69D8slJXXmIM= =TYgT -END PGP SIGNATURE-
Re: Compiling KDE apps: Still not clear...
On Sun, Mar 16, 2003 at 08:19:52PM -0500, Bruce wrote: > I purged and reinstalled all qt/kde -dev packages (the 3.1.2 versions from > ktown.kde.org), but same result. > > Is this right? Or does this indicate something else is messed up on my > system? Sounds like the ktown qt debs are messed up. Chris
Re: Compiling KDE apps: Still not clear...
Following up on my previous query, I looked in /usr/share/qt3/lib/ and /usr/include/qt3/ to see if I could figure out what was causing the compile error. I can't tell if anything is wrong with /usr/include/qt3/, but /usr/share/qt3/lib/ had the following symlinks which pointed to nonexistent files in /usr/lib/: libqt-mt.so--> ../../../lib/libqt-mt.so.3.1.1 libqt-mt.so.3 --> ../../../lib/libqt-mt.so.3.1.1 libqt-mt.so.3.1--> ../../../lib/libqt-mt.so.3.1.1 libqt.so.3 --> ../../../lib/libqt.so.3.1.1 libqt.so.3.1 --> ../../../lib/libqt.so.3.1.1 However, the libqt and libqt-mt files in /usr/lib/ are libqt-mt.so.3.1.2 and libqt.so.3.1.2 I tried adding symlinks in /usr/lib (libqt-mt.so.3.1.1 --> libqt-mt-so.3.1.2) but still got the same compile errors. I purged and reinstalled all qt/kde -dev packages (the 3.1.2 versions from ktown.kde.org), but same result. Is this right? Or does this indicate something else is messed up on my system? Bruce
Compiling KDE apps: Still not clear...
... on what I need to install. I am running KDE 3.1.1 from Ralf's Woody
packages, on a primarily Woody system, with some packages from Sid.
I have read through the various posts this month, and have tried to follow
the advice given, but still can't manage to get past this configure error:
checking for Qt... configure: error: Qt (>= Qt 3.0.2) (library qt-mt) not
found. Please
check your installation!
For more details about this problem, look at the end of config.log.
Make sure that you have compiled Qt with thread support!
(The details from config.log are set out below)
I do have the following packages installed, from Ralf's repository:
libqt3-compat-headers
libqt3-headers
libqt3-mt-dev
libqt3-plugins-headers
qt3-apps-dev
kdebase-dev
kdelibs4-dev
kdemultimedia-dev
kdegraphics-dev
(I didn't install libqt3-dev, because it conflicts with some of the above;
I installed the above packages as they were the packages suggested on this
list. What is libqt3-dev for??)
I get the above error whether I run
./configure
or
./configure --prefix=/usr --with-qt-includes=/usr/include/qt3
or
./configure --prefix=/usr --with-qt-includes=/usr/include/qt3
--with-qt-libraries=/usr/share/qt3/lib
I also tried running
export QTDIR=/usr/share/qt3
first, but I still got the same message indicated above.
For the record, the program I am trying to install is kcdlabel
v.2.11-KDE3. The relevant excerpt from config.log is:
configure:21511: checking for Qt
configure: 21578: /usr/include/qt3/qstyle.h
taking that
configure:21688: rm -rf SunWS_cache; g++ -o conftest -Wnon-virtual-dtor
-Wno-long-long -Wbad-function-cast -Wundef -Wall -pedantic -W
-Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -O2
-fno-exceptions -fno-check-new -I/usr/include/qt3 -I/usr/X11R6/include
-DQT_THREAD_SUPPORT -D_REENTRANT -L/usr/share/qt3/lib -L/usr/X11R6/lib
conftest.cc -lqt-mt -lpng -lz -lm -ljpeg -ldl -lXext -lX11 -lSM -lICE
-lresolv -lpthread 1>&5
/tmp/cc8TDEIj.o(.text+0xe): In function `main':
: undefined reference to `QString::null'
/tmp/cc8TDEIj.o(.text+0x13): In function `main':
: undefined reference to `QStyleFactory::create(QString const&)'
/tmp/cc8TDEIj.o(.text+0x20): In function `main':
: undefined reference to `QCursor::QCursor[in-charge](int)'
/tmp/cc8TDEIj.o(.text+0x28): In function `main':
: undefined reference to `QCursor::~QCursor [in-charge]()'
collect2: ld returned 1 exit status
configure:21691: $? = 1
configure: failed program was:
#include "confdefs.h"
#include
#include
#include
#include
#include
#if ! (QT_VERSION >= 303)
#error 1
#endif
int main() {
(void)QStyleFactory::create(QString::null);
QCursor c(Qt::WhatsThisCursor);
return 0;
}
configure:21731: error: Qt (>= Qt 3.0.3) (library qt-mt) not found. Please
check your installation!
For more details about this problem, look at the end of config.log.
Make sure that you have compiled Qt with thread support!
Bruce
Re: compiling kde-apps without --prefix=/usr
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 21 October 2002 01:06 pm, Andreas Richter wrote: > i think, that my system (woody, kde3.0.4 from kde.org) don't search in the > /usr/local/kde-tree. > what can i do to add these directory-structur to my system? > under /etc/profile i have try the > KDEDIRS=/usr/:/usr/local/kde > but this don't work :( Are you sure KDEDIRS is getting set and exported? Do by any chance login via KDM? If you login via KDM, you will need to create a file that sets up your environment in /etc/X11/Xsession.d/. For example: # /etc/x11/Xsession.d/10local-environment export KDEDIRS=/usr/local/kde:/usr/local:/usr - -- Nathaniel W. Turner http://www.houseofnate.net/ Tel: +1 508 579 1948 (mobile) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9vwqH25cAeUrFyDIRAnfiAJ4ht7woYMCP1HdZSRfnWyO4nwbUfgCg1sa4 Wc7DZgsuDQJeide4OqiFd+k= =5cIp -END PGP SIGNATURE-
Re: compiling kde-apps without --prefix=/usr
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 21. Oktober 2002 19:50 schrieb Hendrik Sattler: > Am Montag, 21. Oktober 2002 19:23 schrieb Thomas Ritter: > > Just make a package. Go to the source dir of your app you want to compile > > and type "deb-make". A directory named debian/ is being created. Call > > "debian/rules binary" and your package will be created. > > I'd rather vote for using dh_make to create the debian subdir and debuild > (or dpkg-buildpackage -rfakeroot) to acutally build the package. Thanks for answers. I tried both versions of package-creation. but which is the preferred one? in other words which mehtod use the debian package maintainer? - -- Gruss/Greetings Andreas Richter OSZine - Das deutschsprachige Open Source Magazin (http://www.oszine.de) GnuPG-PubKey: http://www.oszine.de/gpg/ar.gpg -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9tcO5DPI8V3uhLdkRAsaSAJ0QPYr/T3bmOzbB3b5xK19V+PTC9gCg54Mb Hx9GNGunM5OMgsYsdUo5Wc8= =nSaY -END PGP SIGNATURE-
Re: compiling kde-apps without --prefix=/usr
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 21. Oktober 2002 19:23 schrieb Thomas Ritter: > if I understand it correctly, you want to separate packages from > self-compiled binaries, but KDE likes to have all these things in one place > ;) > Just make a package. Go to the source dir of your app you want to compile > and type "deb-make". A directory named debian/ is being created. Call > "debian/rules binary" and your package will be created. Any configure > options you want to set, you can set in the shell script debian/rules. I'd rather vote for using dh_make to create the debian subdir and debuild (or dpkg-buildpackage -rfakeroot) to acutally build the package. To get something useful, he should really edit those debian/* files, e.g. to have the right description :) HS - -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.schulnetz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9tD5Tzvr6q9zCwcERAkWZAKCmBrCMWD4Q+hesOgxic4MLKYHT4wCfaZvg nSqFkbOZvDvimZ0taFTT2f8= =tI0m -END PGP SIGNATURE-
Re: compiling kde-apps without --prefix=/usr
Hi, if I understand it correctly, you want to separate packages from self-compiled binaries, but KDE likes to have all these things in one place ;) Just make a package. Go to the source dir of your app you want to compile and type "deb-make". A directory named debian/ is being created. Call "debian/rules binary" and your package will be created. Any configure options you want to set, you can set in the shell script debian/rules. -- - Thomas Ritter
compiling kde-apps without --prefix=/usr
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi list, i will compile, install and use ;) a kde-application that not in the official woody. (kile). when i make the normal procedure ./configure && make && su && make install then my computer installs the binarys under the /usr/local/kde file-hierarchie. that's ok and imho standard. but in my kde-menu i can't find an entry like "kile" to run the program. under the console i can run the program with /usr/local/kde/bin/kile but without many of the pictures and without menu i think, that my system (woody, kde3.0.4 from kde.org) don't search in the /usr/local/kde-tree. what can i do to add these directory-structur to my system? under /etc/profile i have try the KDEDIRS=/usr/:/usr/local/kde but this don't work :( the same problem i have with kdevelop... can anybody help me? thanks & - -- Gruss/Greetings Andreas Richter OSZine - Das deutschsprachige Open Source Magazin (http://www.oszine.de) GnuPG-PubKey: http://www.oszine.de/gpg/ar.gpg -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9tDQrDPI8V3uhLdkRAqKaAKDCkLsHeYqlBLoPFCMndIj5Wg6hwACgi3DM PakpEyVgRQC8LqOY5zPGMQU= =gUNZ -END PGP SIGNATURE-
