Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc (GCC) 3.4.2  (Gentoo Linux 3.4.2-r2, ssp-3.4.1-1, pie-8.7.6.5) 
OS:                Linux

On my Linux system, there are symbolic links from libqt to libqt-mt, in order to make older problems work that don't know about qt-mt. This causes problems when I try to build kdebindings:

Making all in python
make[2]: Entering directory `/usr/src/kdecvs/build/kdebindings/python'
cd sip && export QTDIR=/usr/qt/3/ && /usr/bin/python configure.py -b /usr/kde/newcvs/bin -d /usr/lib/python2.3/site-packages
-e `echo -I/usr/include/python2.3 | sed s/-I//` -v /usr/kde/newcvs/share/sip/
Error: These Qt libraries were found: qt qt-mt. Use the -l argument to
explicitly specify which you want to use.
This is SIP 4.0.1 for Python 2.3.4 on linux2.
make[2]: *** [sipdone] Error 1
make[2]: Leaving directory `/usr/src/kdecvs/build/kdebindings/python'

Now I can work around that by changing the kdebindings/python/Makefile to include the option -lqt-mt in the following line:

sipdone:
        cd sip && export QTDIR=${qt_dir} && /usr/bin/python configure.py -b ${exec_prefix}/bin -d ${site_packages} -e ${pytho
n_inc_dir} -v ${sip_dir}

But this manual intervention breaks automatic build systems such as Gentoo's portage or kdecvs-build.

Would there be a way to automate this, or fix the configuration system such that it will recognize libqt and libqt-mt are the same files, or maybe just prefer the threaded version anyway if both are found?