+++ This bug was initially created as a clone of Bug #169132 +++ A large class of kde applications have issues building properly on x86_64 because they have trouble finding qt (usually lib != lib64 assumptions, etc). The workaround is usually to either define env vars QTINC/QTLIB (or use ./configure --with-qt-includes/--with-qt-libraries) pointing to the right place. A lot of duplicated/extra effort could be avoided if QTINC and QTLIB were already (correctly) defined in /etc/profile.d/qt.(sh|csh), adding lines like # Qt initialization script (sh) if [ -z "$QTDIR" ] ; then QTDIR="`/usr/bin/pkg-config --variable=prefix qt-mt`" QTINC="`/usr/bin/pkg-config --variable=includedir qt-mt`" QTLIB="`/usr/bin/pkg-config --variable=libdir qt-mt`" if ! echo ${PATH} | /bin/grep -q $QTDIR/bin ; then PATH=${QTDIR}/bin:${PATH} fi export QTDIR QTINC QTLIB PATH fi # Qt initialization script (csh) if ( $?QTDIR ) then exit endif setenv QTDIR `/usr/bin/pkg-config --variable=prefix qt-mt` setenv QTINC `/usr/bin/pkg-config --variable=includedir qt-mt` setenv QTLIB `/usr/bin/pkg-config --variable=libdir qt-mt` if ( "${path}" !~ *$QTDIR/bin* ) then set path = ( $QTDIR/bin $path ) endif
I know updates for RHEL4 take longer, but gee wiz, it's now approaching a *year* since filing this small, simple enhancement request. Heck, now upstreams are using this as an excuse to not fix their configure scripts ( see http://bugs.kde.org/136377 ).
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0026.html