I'm trying to build the 3.5.13 packages from the tarballs. I keep seeing the following error:
checking for Qt... checking for pkg-config... /usr/bin/pkg-config configure: error: Qt (>= Qt 4.3 and < 5.0) (library QtCore -lQtGui -lQtNetwork -ltqt-mt) not found. Please check your installation!
I looked at the logs, configure, etc., but I don't see anything obvious.
What is the magic trick?
Darrell
Le Fri, 4 Nov 2011 10:19:07 -0700 (PDT), Darrell Anderson humanreadable@yahoo.com a écrit :
I'm trying to build the 3.5.13 packages from the tarballs. I keep seeing the following error:
checking for Qt... checking for pkg-config... /usr/bin/pkg-config configure: error: Qt (>= Qt 4.3 and < 5.0) (library QtCore -lQtGui -lQtNetwork -ltqt-mt) not found. Please check your installation!
I looked at the logs, configure, etc., but I don't see anything obvious.
What is the magic trick?
You probably built the Qt4 tqtinterface. My build script includes -DWITH_QT3=1 which tells tqtinterface to use Qt3 instead.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Le Sat, 5 Nov 2011 06:16:18 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Le Fri, 4 Nov 2011 10:19:07 -0700 (PDT), Darrell Anderson humanreadable@yahoo.com a écrit :
I'm trying to build the 3.5.13 packages from the tarballs. I keep seeing the following error:
checking for Qt... checking for pkg-config... /usr/bin/pkg-config configure: error: Qt (>= Qt 4.3 and < 5.0) (library QtCore -lQtGui -lQtNetwork -ltqt-mt) not found. Please check your installation!
I looked at the logs, configure, etc., but I don't see anything obvious.
What is the magic trick?
You probably built the Qt4 tqtinterface. My build script includes -DWITH_QT3=1 which tells tqtinterface to use Qt3 instead.
Actually I did just run into the same issue trying to build kdegames. According to config.log the autoconf system is too dumb to read the tqt include dirs from the tqt.pc file, whereas the CMake build system gets it right. And since the tqt test is supposed to fail iff the tqtinterface is the Qt4 one, configure wrongly assumes tqt is tqt4 and searches for Qt4.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Actually I did just run into the same issue trying to build kdegames. According to config.log the autoconf system is too dumb to read the tqt include dirs from the tqt.pc file, whereas the CMake build system gets it right. And since the tqt test is supposed to fail iff the tqtinterface is the Qt4 one, configure wrongly assumes tqt is tqt4 and searches for Qt4.
Many of of the 3.5.13 tarballs do not support cmake. Seems then the best approach when using the 3.5.13 tarballs is to build without QT4 installed. Should we fix this in SVN? Is there a patch for the 3.5.13 tarballs to work around this?
Darrell
Le Sat, 5 Nov 2011 07:13:51 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Le Sat, 5 Nov 2011 06:16:18 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Le Fri, 4 Nov 2011 10:19:07 -0700 (PDT), Darrell Anderson humanreadable@yahoo.com a écrit :
I'm trying to build the 3.5.13 packages from the tarballs. I keep seeing the following error:
checking for Qt... checking for pkg-config... /usr/bin/pkg-config configure: error: Qt (>= Qt 4.3 and < 5.0) (library QtCore -lQtGui -lQtNetwork -ltqt-mt) not found. Please check your installation!
I looked at the logs, configure, etc., but I don't see anything obvious.
What is the magic trick?
You probably built the Qt4 tqtinterface. My build script includes -DWITH_QT3=1 which tells tqtinterface to use Qt3 instead.
Actually I did just run into the same issue trying to build kdegames. According to config.log the autoconf system is too dumb to read the tqt include dirs from the tqt.pc file, whereas the CMake build system gets it right. And since the tqt test is supposed to fail iff the tqtinterface is the Qt4 one, configure wrongly assumes tqt is tqt4 and searches for Qt4.
Partial threadjacking: Removing Qt4 didn't solve the build issues as it did for you (perhaps tqtinterface should be rebuilt after Qt4 removal ?), but I managed to build kdemultimedia with the following commands (still without Qt4): $ make -f Makefile.cvs $ sed -i 's#/usr/include/tqt#/opt/kde3/include/tqt#g' configure $ ./configure --prefix=/opt/kde3 --with-additional-libs=/opt/kde3/lib $ make -j5 LDFLAGS="-Wl,--as-needed -lqt-mt -lkdecore -lkdeui -lglib-2.0 -lmad -lvorbisfile -lpthread -lDCOP -lkmime -lgthread -lvorbis -lkio" (apparently the Makefile forgot the libs with which the programs and DSO need a link…). TLDR: autotools == huge mess.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Le Wed, 9 Nov 2011 23:26:24 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Le Sat, 5 Nov 2011 07:13:51 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Le Sat, 5 Nov 2011 06:16:18 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Le Fri, 4 Nov 2011 10:19:07 -0700 (PDT), Darrell Anderson humanreadable@yahoo.com a écrit :
I'm trying to build the 3.5.13 packages from the tarballs. I keep seeing the following error:
checking for Qt... checking for pkg-config... /usr/bin/pkg-config configure: error: Qt (>= Qt 4.3 and < 5.0) (library QtCore -lQtGui -lQtNetwork -ltqt-mt) not found. Please check your installation!
I looked at the logs, configure, etc., but I don't see anything obvious.
What is the magic trick?
You probably built the Qt4 tqtinterface. My build script includes -DWITH_QT3=1 which tells tqtinterface to use Qt3 instead.
Actually I did just run into the same issue trying to build kdegames. According to config.log the autoconf system is too dumb to read the tqt include dirs from the tqt.pc file, whereas the CMake build system gets it right. And since the tqt test is supposed to fail iff the tqtinterface is the Qt4 one, configure wrongly assumes tqt is tqt4 and searches for Qt4.
Partial threadjacking: Removing Qt4 didn't solve the build issues as it did for you (perhaps tqtinterface should be rebuilt after Qt4 removal ?), but I managed to build kdemultimedia with the following commands (still without Qt4): $ make -f Makefile.cvs $ sed -i 's#/usr/include/tqt#/opt/kde3/include/tqt#g' configure $ ./configure --prefix=/opt/kde3 --with-additional-libs=/opt/kde3/lib $ make -j5 LDFLAGS="-Wl,--as-needed -lqt-mt -lkdecore -lkdeui -lglib-2.0 -lmad -lvorbisfile -lpthread -lDCOP -lkmime -lgthread -lvorbis -lkio" (apparently the Makefile forgot the libs with which the programs and DSO need a link…). TLDR: autotools == huge mess.
Same thing for kdegames, with $ make -j5 CXXFLAGS="-I/opt/kde3/include/tqt -include tqt.h" LDFLAGS="-lqt-mt -lkdecore" as build command. In addition of the custom commands, the patch I attached was necessary to successfully build kdegames (with the builds commands I used the DEBUG was probably set to NULL, which makes the comparison DEBUG >= 2 not compile).
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
--- On Wed, 11/9/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
From: /dev/ammo42 mickeytintincolle@yahoo.fr Subject: Re: [trinity-devel] configure: error: Qt (>= Qt 4.3 and < 5.0)... To: trinity-devel@lists.pearsoncomputing.net Date: Wednesday, November 9, 2011, 4:56 PM Le Wed, 9 Nov 2011 23:26:24 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Le Sat, 5 Nov 2011 07:13:51 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr
a écrit :
Le Sat, 5 Nov 2011 06:16:18 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr
a écrit :
Le Fri, 4 Nov 2011 10:19:07 -0700 (PDT), Darrell Anderson humanreadable@yahoo.com
a écrit :
I'm trying to build the 3.5.13 packages
from the tarballs. I
keep seeing the following error:
checking for Qt... checking for pkg-config... /usr/bin/pkg-config
configure: error: Qt (>= Qt
4.3 and < 5.0) (library QtCore
-lQtGui -lQtNetwork -ltqt-mt)
not found. Please check your
installation!
I looked at the logs, configure, etc.,
but I don't see anything
obvious.
What is the magic trick?
You probably built the Qt4 tqtinterface. My
build script includes
-DWITH_QT3=1 which tells tqtinterface to use
Qt3 instead.
Actually I did just run into the same issue
trying to build
kdegames. According to config.log the autoconf
system is too dumb
to read the tqt include dirs from the tqt.pc
file, whereas the
CMake build system gets it right. And since the
tqt test is
supposed to fail iff the tqtinterface is the Qt4
one, configure
wrongly assumes tqt is tqt4 and searches for
Qt4.
Partial threadjacking: Removing Qt4 didn't solve the build issues as it did
for you (perhaps
tqtinterface should be rebuilt after Qt4 removal ?),
but I managed to
build kdemultimedia with the following commands (still
without Qt4):
$ make -f Makefile.cvs $ sed -i 's#/usr/include/tqt#/opt/kde3/include/tqt#g'
configure
$ ./configure --prefix=/opt/kde3
--with-additional-libs=/opt/kde3/lib
$ make -j5 LDFLAGS="-Wl,--as-needed -lqt-mt -lkdecore
-lkdeui
-lglib-2.0 -lmad -lvorbisfile -lpthread -lDCOP -lkmime
-lgthread
-lvorbis -lkio" (apparently the Makefile forgot the
libs with which
the programs and DSO need a link…). TLDR: autotools == huge mess.
Same thing for kdegames, with $ make -j5 CXXFLAGS="-I/opt/kde3/include/tqt -include tqt.h" LDFLAGS="-lqt-mt -lkdecore" as build command. In addition of the custom commands, the patch I attached was necessary to successfully build kdegames (with the builds commands I used the DEBUG was probably set to NULL, which makes the comparison DEBUG >= 2 not compile).
I haven't had any problems building after I removed QT4 and most KDE4 packages.
I intend to make another full run at building the packages to ensure there are no problems.
I think you are using 13.37 where I am using 13.1. I wonder whether there are subtle differences that cause the errors you see?
I hope to try building in a 13.37 virtual machine.
Darrell
Le Wed, 9 Nov 2011 16:29:33 -0800 (PST), Darrell Anderson humanreadable@yahoo.com a écrit :
--- On Wed, 11/9/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
From: /dev/ammo42 mickeytintincolle@yahoo.fr Subject: Re: [trinity-devel] configure: error: Qt (>= Qt 4.3 and < 5.0)... To: trinity-devel@lists.pearsoncomputing.net Date: Wednesday, November 9, 2011, 4:56 PM Le Wed, 9 Nov 2011 23:26:24 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Le Sat, 5 Nov 2011 07:13:51 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr
a écrit :
Le Sat, 5 Nov 2011 06:16:18 +0100, /dev/ammo42 mickeytintincolle@yahoo.fr
a écrit :
Le Fri, 4 Nov 2011 10:19:07 -0700 (PDT), Darrell Anderson humanreadable@yahoo.com
a écrit :
I'm trying to build the 3.5.13 packages
from the tarballs. I
keep seeing the following error:
checking for Qt... checking for pkg-config... /usr/bin/pkg-config
configure: error: Qt (>= Qt
4.3 and < 5.0) (library QtCore
-lQtGui -lQtNetwork -ltqt-mt)
not found. Please check your
installation!
I looked at the logs, configure, etc.,
but I don't see anything
obvious.
What is the magic trick?
You probably built the Qt4 tqtinterface. My
build script includes
-DWITH_QT3=1 which tells tqtinterface to use
Qt3 instead.
Actually I did just run into the same issue
trying to build
kdegames. According to config.log the autoconf
system is too dumb
to read the tqt include dirs from the tqt.pc
file, whereas the
CMake build system gets it right. And since the
tqt test is
supposed to fail iff the tqtinterface is the Qt4
one, configure
wrongly assumes tqt is tqt4 and searches for
Qt4.
Partial threadjacking: Removing Qt4 didn't solve the build issues as it did
for you (perhaps
tqtinterface should be rebuilt after Qt4 removal ?),
but I managed to
build kdemultimedia with the following commands (still
without Qt4):
$ make -f Makefile.cvs $ sed -i 's#/usr/include/tqt#/opt/kde3/include/tqt#g'
configure
$ ./configure --prefix=/opt/kde3
--with-additional-libs=/opt/kde3/lib
$ make -j5 LDFLAGS="-Wl,--as-needed -lqt-mt -lkdecore
-lkdeui
-lglib-2.0 -lmad -lvorbisfile -lpthread -lDCOP -lkmime
-lgthread
-lvorbis -lkio" (apparently the Makefile forgot the
libs with which
the programs and DSO need a link…). TLDR: autotools == huge mess.
Same thing for kdegames, with $ make -j5 CXXFLAGS="-I/opt/kde3/include/tqt -include tqt.h" LDFLAGS="-lqt-mt -lkdecore" as build command. In addition of the custom commands, the patch I attached was necessary to successfully build kdegames (with the builds commands I used the DEBUG was probably set to NULL, which makes the comparison DEBUG >= 2 not compile).
I haven't had any problems building after I removed QT4 and most KDE4 packages.
I intend to make another full run at building the packages to ensure there are no problems.
I think you are using 13.37 where I am using 13.1. I wonder whether there are subtle differences that cause the errors you see?
No, I tried on a 32-bit Slackware 13.1 with the 64-bit 2.6.33.4 kernel from Slackware64 13.1. But I didn't remove any L-series package other than Qt4, it must explain the differences between our results :) I currently dual-boot Slackware 13.1 (with Trinity as main desktop) and Slackware64 13.37 (with KDE4 as main desktop), but with only 64-bit kernels. I did partial builds of Trinity on both systems, and except for the broken 13.37 libical, I didn't see actual differences between 13.1 and 13.37 in terms of building the dependencies, kdebase, kdelibs and kdepim (which are the only packages I built on 13.37); but I won't be able to build full Trinity in 13.37 because it is my KDE4 system, from which I won't remove KDE4 packages.
I hope to try building in a 13.37 virtual machine.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
No, I tried on a 32-bit Slackware 13.1 with the 64-bit 2.6.33.4 kernel from Slackware64 13.1. But I didn't remove any L-series package other than Qt4, it must explain the differences between our results :) I currently dual-boot Slackware 13.1 (with Trinity as main desktop) and Slackware64 13.37 (with KDE4 as main desktop), but with only 64-bit kernels. I did partial builds of Trinity on both systems, and except for the broken 13.37 libical, I didn't see actual differences between 13.1 and 13.37 in terms of building the dependencies, kdebase, kdelibs and kdepim (which are the only packages I built on 13.37); but I won't be able to build full Trinity in 13.37 because it is my KDE4 system, from which I won't remove KDE4 packages.
I hope to try building in a 13.37 virtual machine.
Okay. I'll check which packages in my build environment I removed from the stock 13.1 system.
I am not running 64-bit. Likewise with my 13.37 virtual machine. :(
Several days ago I filed a bug report (582) that I could not build Trinity without removing qt4. As my 13.1 build environment does not include a bunch of KDE4 packages, I still have to test using Trinity in a 13.1 stock system to see whether any obvious QT4/KDE4 conflicts exist. I have yet to test Trinity 3.5.13 at all. :) I'm running another complete build pass right now to ensure that part is okay.
Darrell
I am not running 64-bit. Likewise with my 13.37 virtual machine. :(
Actually you have at least one x86_64 compatible machine: the HTPC you describe in http://humanreadable.nfshost.com/journal/2009/2009-014.htm You don't even have to install a new system to make tests on Slackware64, you can just -boot with a 64-bit kernel (you can install directly the Slackware64 kernel packages with installpkg; some Phoronix benchmarks interestingly report much improved performance using the 64-bit kernel rather than the 32-bit one, with Ubuntu kernels and the same 32-bit Ubuntu userland) -install a Slackware64 chroot: http://slackworld.berlios.de/2007/chroot_howto.html explains how to set up a Slackware chroot without doing a regular install. The combination of 64-bit kernel/32-bit main system/64-bit chroot system is the one I am currently using, so I can confirm it works :)
I haven't had any problems building after I removed QT4 and most KDE4 packages.
I intend to make another full run at building the packages to ensure there are no problems.
I think you are using 13.37 where I am using 13.1. I wonder whether there are subtle differences that cause the errors you see?
I hope to try building in a 13.37 virtual machine.
Darrell
I belive the difference is the location of tqt files on your system (/usr)
---------------------------------------------------------------- Mieszkanie w centrum za 600 zl/m-c http://linkint.pl/f2a7e
I'm trying to build the 3.5.13 packages from the
tarballs. I keep
seeing the following error:
checking for Qt... checking for pkg-config...
/usr/bin/pkg-config
configure: error: Qt (>= Qt 4.3 and < 5.0)
(library QtCore -lQtGui
-lQtNetwork -ltqt-mt) not found. Please check your
installation!
I looked at the logs, configure, etc., but I don't see
anything
obvious.
What is the magic trick?
You probably built the Qt4 tqtinterface. My build script includes -DWITH_QT3=1 which tells tqtinterface to use Qt3 instead.
To clarify, the error occurs with those tarballs that are built with autotools. I did not find an equivalent -DWITH_QT3 option in the autotools configure script.
I am able to avoid the error with those tarballs by removing the QT4 package. I had read that Trinity can be built with QT4 installed, but perhaps that applies only to cmake and not autotools?
Darrell
-
/dev/ammo42 -
alekow -
Darrell Anderson