Tim, Darrell, All,
python-tqt fails to build from source. It looks like it may be related to a sip problem (see 1st two lines below). I haven't changed my build scripts of either sip or python-tqt. What should I check? Full error follows:
sip: TQ_LONG is undefined Error: Unable to create the C++ code. This is the GPL version of PyTQt 3.18.1 (licensed under the GNU General Public License) for Python 2.7.3 on linux2.
Type 'L' to view the license. Type 'yes' to accept the terms of the license. Type 'no' to decline the terms of the license.
Do you accept the terms of the license? qextscintillaglobal.h could not be found in /opt/tqt3/include and so the qtext module will not be built. If TQScintilla is installed then use the -n argument to explicitly specify the correct directory. Checking to see if the qtcanvas module should be built... Checking to see if the qtnetwork module should be built... Checking to see if the qttable module should be built... Checking to see if the qtxml module should be built... Checking to see if the qtgl module should be built... Checking to see if the qtui module should be built... Checking to see if the qtsql module should be built... Checking to see if the TQAssistantClient class is available... Creating features file... Checking to see if the TQCDEStyle class is built in... Checking to see if the TQCDEStyle class is built in... Checking to see if the TQInterlaceStyle class is built in... Checking to see if the TQInterlaceStyle class is built in... Checking to see if the TQMotifStyle class is built in... Checking to see if the TQMotifStyle class is built in... Checking to see if the TQMotifPlusStyle class is built in... Checking to see if the TQMotifPlusStyle class is built in... Checking to see if the TQPlatinumStyle class is built in... Checking to see if the TQPlatinumStyle class is built in... Checking to see if the TQSGIStyle class is built in... Checking to see if the TQSGIStyle class is built in... Checking to see if the TQWindowsXPStyle class is built in... Checking to see if the TQWindowsXPStyle class is built in... Checking to see if the TQWindowsStyle class is built in... Checking to see if the TQWindowsStyle class is built in... TQt v3.4.0 free edition is being used. SIP 4.10.5 is being used. These PyTQt modules will be built: qt qtcanvas qtnetwork qttable qtxml qtgl qtui qtsql. Support for these TQt classes has been disabled: TQInterlaceStyle TQWindowsXPStyle. The PyTQt modules will be installed in /usr/lib/python2.7/site-packages. The PyTQt .sip files will be installed in /usr/share/sip. The TQt header files are in /opt/tqt3/include. The tqt-mt TQt library is in /opt/tqt3/lib. pyuic will be installed in /usr/bin. pylupdate will be installed in /usr/bin. Generating the C++ source for the qt module...
python-tqt fails to build from source. It looks like it may be related to a sip problem (see 1st two lines below). I haven't changed my build scripts of either sip or python-tqt. What should I check? Full error follows:
sip: TQ_LONG is undefined ...
There are two ongoing patch efforts affecting current build efforts. Tim alluded to them in a previous post. The related bug reports:
843 Tools provided by Qt3 conflict with ones from Qt4 1048 Digikam: Unexpected Q_LLONG messages
The first bug report addresses the 15 executables installed by (T)Qt3, all used to build Trinity apps. Tim renamed those executables. This will cause some temporary heartburn as we build and discover which packages can't find the new names.
The second bug report originally addressed some unhealthy output spew from digikam, but the required patch affected almost all packages. Tim has been addressing those, as you can see from the latest patch commits web page. These patches also will cause some temporary heartburn.
Yesterday I ran a partial build set. I could not build any of the tdebindings support packages, just as you now notice. I also could not build koffice.
The best thing to do is post the failures here or to the respective bug report. Look at commit 75df7496 to notice the types of failures to expect related to bug report 1048:
http://www.trinitydesktop.org/patches/1339969374:75df74966c28283d751c7e87630...
I am getting ready to run another build set and will be posting failures and proposed patches as they occur. :-)
Darrell
On 06/19/2012 07:56 PM, Darrell Anderson wrote:
python-tqt fails to build from source. It looks like it may be related to a sip problem (see 1st two lines below). I haven't changed my build scripts of either sip or python-tqt. What should I check? Full error follows:
sip: TQ_LONG is undefined ...
There are two ongoing patch efforts affecting current build efforts. Tim alluded to them in a previous post. The related bug reports:
843 Tools provided by Qt3 conflict with ones from Qt4 1048 Digikam: Unexpected Q_LLONG messages
The first bug report addresses the 15 executables installed by (T)Qt3, all used to build Trinity apps. Tim renamed those executables. This will cause some temporary heartburn as we build and discover which packages can't find the new names.
The second bug report originally addressed some unhealthy output spew from digikam, but the required patch affected almost all packages. Tim has been addressing those, as you can see from the latest patch commits web page. These patches also will cause some temporary heartburn.
Yesterday I ran a partial build set. I could not build any of the tdebindings support packages, just as you now notice. I also could not build koffice.
The best thing to do is post the failures here or to the respective bug report. Look at commit 75df7496 to notice the types of failures to expect related to bug report 1048:
http://www.trinitydesktop.org/patches/1339969374:75df74966c28283d751c7e87630...
I am getting ready to run another build set and will be posting failures and proposed patches as they occur. :-)
Darrell
Tim, Darrell,
I updated http://bugs.pearsoncomputing.net/show_bug.cgi?id=1048 and included build logs for the following FTBFS:
tde-kipi-plugins-14.0.0_dev-1-i686-build.log tde-avahi-tqt-14.0.0_dev-1-i686-build.log tde-gtk-qt-engine-14.0.0_dev-1-i686-build.log tde-python-tqt-14.0.0_dev-1-i686-build.log tde-tdegraphics-14.0.0_dev-1-i686-build.log tde-tdesvn-14.0.0_dev-1-i686-build.log
Hopefully all the renaming will pay off with increased acceptance/support of TDE by the distros. The more it is used, the more it is improved :)