Are any processes using 100% CPU while you are waiting? If so, which program is using the CPU?
I didn't write the pykdeextensions/python-kde3 package; in fact I have next to zero Python programming ability, so that is a package I don't touch unless something is seriously wrong.
I downloaded 3.16.7 and tried compiling that rather than from SVN. Same results. Same stall point.
Top showed the cc1plus compiler hogging 99% CPU time and 8% memory.
This time I waited about 15 minutes and then the build continued.
Possibly then the svn version is okay too.
After continuing to compile --- for only a second --- there was another long stall. The pause was with the kdeui directory.
According to the build instructions (http://www.riverbankcomputing.co.uk/static/Docs/PyKDE3/install.html), compiling should take 15 minutes to one hour.
I waited an hour. Nothing.
I decided to force non-concatenation with the -i switch.
At least the -i switch is verbose and I could see things happening. That mode also was easier on the CPU.
The package failed to build, but I knew right away. More than likely the concatenated version failed too and there was no message.
SIP 4.11.1 and PyQT3 3.18.1 compiled fine.
Log attached.
According to the failure error, kinputidalog.h has an undeclared class QValidator. kinputidalog.h is installed from kdelibs.
<snip>
I decided to force non-concatenation with the -i switch.
At least the -i switch is verbose and I could see things happening. That mode also was easier on the CPU.
You can build it that way without any problems.
The package failed to build, but I knew right away. More than likely the concatenated version failed too and there was no message.
SIP 4.11.1 and PyQT3 3.18.1 compiled fine.
Log attached.
According to the failure error, kinputidalog.h has an undeclared class QValidator. kinputidalog.h is installed from kdelibs.
OK, I have added a change to kdelibs in revision 1178028 to force inclusion of the tqt.h header when pykde uses the kinputdialog.h file. You will need to rebuild/reinstall kdelibs, then try to rebuild pykde again.
Tim
According to the failure error, kinputidalog.h has an
undeclared class
QValidator. kinputidalog.h is installed from kdelibs.
OK, I have added a change to kdelibs in revision 1178028 to force inclusion of the tqt.h header when pykde uses the kinputdialog.h file. You will need to rebuild/reinstall kdelibs, then try to rebuild pykde again.
Yay!
I got python-kde3 (pykde3) to build!
I added the following:
#include <tqt.h>
to three files:
/usr/include/klineeditdlg.h /usr/include/kcmenumngr.h /usr/include/kfileiconview.h
All three header files are part of kdelibs. This would be the same change as made in kinputdialog.h.
If you officially patch those files I'll be sure to run another pass at building.
I built this pykde3 package from svn. According to configure.py, the svn version is 3.16.6 (pykde_version_str = "3.16.6"). The latest version provided upstream is 3.16.7 (http://www.riverbankcomputing.co.uk/software/pykde/download3). Oddly, the upstream providers forgot to update the embedded version variable, which is still at 3.16.6 despite the tarball saying 3.16.7.
Questions:
1. The folks who create python-kde3 refer to the package as pykde3. For consistency, should Trinity use the same name?
2. Should Trinity continue providing a version when upstream (http://www.riverbankcomputing.co.uk/software/pykde/intro) maintains package sources? You're not providing SIP and PyQt3 for that same reason.
I also built the upstream 3.16.7 with my new patches.
I still need to test building kdebindings against the three dependency packages, with both the svn version and upstream version of pykde3.
If you officially patch those files I'll be sure to run another pass at building.
Changes are in SVN; you may want to rebuild everything just to make sure nothing obscure broke.
I built this pykde3 package from svn. According to configure.py, the svn version is 3.16.6 (pykde_version_str = "3.16.6"). The latest version provided upstream is 3.16.7 (http://www.riverbankcomputing.co.uk/software/pykde/download3). Oddly, the upstream providers forgot to update the embedded version variable, which is still at 3.16.6 despite the tarball saying 3.16.7.
Questions:
- The folks who create python-kde3 refer to the package as pykde3. For
consistency, should Trinity use the same name?
Yes.
- Should Trinity continue providing a version when upstream
(http://www.riverbankcomputing.co.uk/software/pykde/intro) maintains package sources? You're not providing SIP and PyQt3 for that same reason.
No.
However, I cannot make that large of a change this close to release. The appropriate action will be taken for 3.5.13.
Thanks for all your hard work in getting this to compile!
Tim
- Should Trinity continue providing a version when
upstream
maintains
package sources? You're not providing SIP and PyQt3
for that same reason.
No.
However, I cannot make that large of a change this close to release. The appropriate action will be taken for 3.5.13.
Okay. I'm writing the Slackware build scripts to use the upstream version of pykde3 rather than svn. That way there will be no changes when you delete python-kde3 (pykde3) from svn.
-
Darrell Anderson -
Timothy Pearson