Bug 101077

Version:           3.4.0-rc1 (using KDE KDE 3.4.0)
Installed from:    Compiled From Sources
Compiler:          gcc (GCC) 3.3.3 GNU Make 3.80 ; automake (GNU automake) 1.9.5
OS:                Linux

When compiling kdebindings on my Linux distribution, Source Mage, I get the following output when it gets to the python area:

[snip]
Making all in python
make[3]: Entering directory `/usr/src/kdebindings-3.4.0/python'
mkdir sip
mkdir: cannot create directory `sip': File exists
make[3]: [sipdone] Error 1 (ignored)
export builddir=`pwd` ; \
cd ./sip ; \
export QTDIR=/usr/include/ ; \
/usr/bin/python configure.py -b /usr/bin -d /usr/lib/python2.3/site-packages 
-e `echo -I/usr/include/python2.3 | sed s/-I//` -l qt-mt -v /usr/share/sip/ 
-t
"$builddir/sip" INCDIR_QT=/usr/include/qt
Error: The qt-mt Qt library could not be found in /usr/include//lib.
This is SIP 4.1.1 for Python 2.3 on linux2.
make[3]: *** [sipdone] Error 1
make[3]: Leaving directory `/usr/src/kdebindings-3.4.0/python'
make[2]: make[2]: Leaving directory `/usr/src/kdebindings-3.4.0'
*** [all-recursive] Error 1
make[1]: make[1]: Leaving directory `/usr/src/kdebindings-3.4.0'
*** [all] Error 2


If you'll notice, it is exporting QTDIR=/usr/include/, which is the wrong directory (it should be /usr), and then tries to find the libraries in /usr/include//lib.

Where I believe the problem lies is line 8 of python/Makefile.am:
qt_dir = $(dir @qt_includes@)

On my system, that translates to QTDIR==/usr/include/.  When the compile gets to line 28 in python/Makefile.am, the library path is set to /usr/include//lib, which, of course, is incorrect.

When I set line 8 of python/Makefile.am to qt_dir = /usr (and re-ran aclocal, because I have a newer version of automake installed), the compile completed correctly.

I'm not sure what the correct setting is that needs to be on line 8, because I tried several that all failed.  Only when I hard-coded the path did it actually succeed.  I'm sure that's not the correct answer, but I'm sure that you all who know the internals of KDE so much better than I do, will be able to come up with the correct answer.

BTW, I am running 3.4.0-rc1, but I checked CVS HEAD before submitting this bug report, and this problem is still there.