On 19 Jul 2011, Timothy Pearson uttered the following:
It is most certainly buildable!
Check out from the latest SVN and use CMake to build these packages: libtqtinterface arts kdelibs kdebase
Use Automake to build the rest.
Tried that (hence the patches sent earlier today). tqt, arts, kdelibs, dbus-tqt and kdebase built after some patching, but when I hit kdenetwork and tried to build it via autotools I got the FTBFS which started this thread :( and comments from Robert that the SVN trunk of the non-cmakeable modules is not buildable with autotools either at present.
This is not correct. You can (and should) build the packages I mentioned with CMake, and then proceed to build the remaining packages with Autotools. Of course I am only mentioning this within the context of using the latest SVN sources; the older 3.5.12 release is only buildable under Autotools, and is also restricted to working with autoconf < 2.63.
It seems that the autotools machinery is getting something wrong such that TQt is not being picked up properly, I'd guess. (Plainly it works sometimes, because the SVN log contains recent mentions of fixes of FTBFS errors: hence this report.)
I am actually running a full rebuild test as I write this, so if something is not buildable I will find out about it soon. Otherwise, there is a chance that something is different in your setup vs. my setup, and you may need to pass additional configuration flags to the Autotools-dependent Trinity packages.
(btw, I think what you're doing with Trinity is awesome. A parallel- installable KDE3 eventually atop Qt4: it's what the KDE devs should have done all along :) )
Thanks! Encouragement is always appreciated here. :)
Tim