trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: September 2010

Re: [trinity-devel] python-kde3 (pykde) FTBFS

From: Darrell Anderson <humanreadable@...>
Date: Tue, 21 Sep 2010 15:42:54 -0700 (PDT)
> 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.


      

Attachments: