By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 582 - Can't build 3.5.13 tarballs with autotool with QT4 installed
Summary: Can't build 3.5.13 tarballs with autotool with QT4 installed
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: system (show other bugs)
Version: 3.5.13 [Trinity]
Hardware: Other Other
: P1 critical
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-11-06 11:39 CST by Darrell
Modified: 2012-10-19 15:20 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2011-11-06 11:39:56 CST 
All but the core source tarballs are expected to be built with autotools, but they will not build properly unless QT4 is removed. The cmake build options include the -DWITH_QT3 and -DUSE_QT3 options but there is no equivalent option for autotools. The resulting 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!
Comment 1 L0ner 2011-12-08 17:58:55 CST 
Same on Arch. Probably it's caused by autotools detecting incorrectly TQt4 (instead of 3) and thus searching for Qt4.
Comment 2 Darrell 2012-01-10 02:18:14 CST 
I think the workaround is to add the following to the configure options:

--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
Comment 3 Darrell 2012-01-12 20:21:30 CST 
I have rebuilt Trinity 3.5.13 packages several times. I have Qt4 installed in my build environment. Since adding the three aforementioned configure options some time ago to all of my remaining automake build scripts, I have not seen the error messages cited in the original report.

I recommend tagging this report as resolved, unless others can show the problem still occurs when using the three configure options mentioned in the previous comment.

The wiki has been updated to include this information. :)
Comment 4 Timothy Pearson 2012-01-12 21:13:50 CST 
Marking as resolved.