pykde-3.5.0.ebuild hangs for me at build time, consuming large amounts of memory. The culprit appears to be the following line during compilation: g++ -c -Wno-deprecated-declarations -pipe -O2 -march=i686 -fomit-frame-pointer -fPIC -O2 -march=i686 -fno-strict-aliasing -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I. -I/var/tmp/portage/pykde-3.5.0/work/pykde-3.5.0/python/pykde/extra/kdecvs -I/usr/kde/3.5/include -I/usr/include/python2.4 -I/usr/qt/3/include -I/usr/X11R6/include -o sipkdeuipart1.o sipkdeuipart1.cpp According to an entry in the PyKDE troubleshooting docs, this can be fixed using the '-i' switch when running 'python configure.py', with the tradeoff of increased compilation time: http://www.riverbankcomputing.com/Docs/PyKDE3/trouble.html Please find attached a simple patch to the ebuild that makes this switch mandatory. The way I added this might not be optimal, I am happy to change things around as required.
Created attachment 86568 [details, diff] pykde-3.5.0-concatenation patch pykde-3.5.0.ebuild patch to make the '-i' switch mandatory for the ebuild.
I had the same problem compiling, but the patch works fine (didn't notice any major changes in compile-time either).
(In reply to comment #2) > I had the same problem compiling, but the patch works fine (didn't notice any > major changes in compile-time either). > Both the PyKDE versions in the tree has the same "bug" (dev-python/pykde and kde-base/pykde).
Caleb has added the switch a while ago, but I'd like to know what you mean by "hangs" and "lots of memory". Yes, it needs a bit more memory, but the overall build time is a lot lower - unless you have a crappy old box low on memory I wouldn't even run KDE on. So, what's your setup?
See comment 4.
*** Bug 169840 has been marked as a duplicate of this bug. ***
Still the same with dev-python/pykde
In the case of my laptop, I could compile dev-python/pykde with MAKEOPTS="-j1". My other machine didn't compile the package even with that change and showed the same result als described in Bug 169840. Using the -i switch made this machine also compile the package; so I propose to set this switch as default. It also seems to me more reasonable to build small pieces and link them than building huge pieces of the software at once eating all the memory.
Just the same problem. Solved with "-i". May be it does worth adding to ebuild?
Just had this issue on amd64 with 1G of RAM. Trying to emerge dev-python/pykde caused cc1plus to use in excess of 800M. Adding the -i flag to configure.py fixed this sip 4.5.2-r1 pyqt 3.17 gcc 4.1.2
Does this still apply to kde-3.5.7? If using kde-base/pykde, do you have the kdeenablefinal use flag?
kde-base/pykde-3.5.6 and 3.5.7 already have the -i switch. I've just added it to dev-python/pykde-3.16.0 as well. Furthermore, a needed DEPEND on either konsole or kdebase was missing. I've fixed that as well.
