| View previous topic :: View next topic |
| Author |
Message |
[herb]
Apprentice
Joined: 14 Oct 2003
Posts: 173
Location: Ontario, Canada
|
 Posted: Wed Dec 03, 2003 10:36 am Post subject: PyKDE emerge issue |
 |
|
Hi, I'm having a probelm emerging the KDE python library.
For three days in a row now, I have tried to emerge PyKDE. All of its dependencies, including PyQT emerged fine. However, I always set "emerge pykde" before I go to bed, and when I wake up... I am back at the KDM login screen (X has obviously restarted), and when I emerge -s pykde... it says it isnt installed.
Could this be because I am emerging it within KDE? Do I need to do it from a normal command prompt? I am at my wits end here 
Any help would be appreciated... I dont even know where to begin troubleshooting this, as I dont have any output I can read for errors.
Thanks,
Scott
| Code: | | CFLAGS="-O3 -march=pentium3 -fprefetch-loop-arrays -funroll-loops -pipe" |
_________________
PC: Antec 350W PSU, AMD Athlon64 3000+, ASUS K8V Deluxe Mobo, 512MB PC3200@400MHz, ATI Radeon 9800 Pro 128MB, 80GB Maxtor HDD @ 7200RPM |
|
| Back to top |
|
 |
[herb]
Apprentice
Joined: 14 Oct 2003
Posts: 173
Location: Ontario, Canada
|
| Posted: Thu Dec 04, 2003 5:15 am Post subject: |
|
|
*bump*
No one has any idea what may be going on? It's driving me crazy!
_________________
PC: Antec 350W PSU, AMD Athlon64 3000+, ASUS K8V Deluxe Mobo, 512MB PC3200@400MHz, ATI Radeon 9800 Pro 128MB, 80GB Maxtor HDD @ 7200RPM |
|
| Back to top |
|
|
Carlo
Developer
Joined: 12 Aug 2002
Posts: 3356
|
| Posted: Thu Dec 04, 2003 11:07 am Post subject: |
|
|
Without any information what happened, obviously not.
 emerge pykde 2>&1 | tee logfile
Carlo
_________________
Please make sure that you have searched for an answer to a question after reading all the relevant docs. |
|
| Back to top |
|
|
[herb]
Apprentice
Joined: 14 Oct 2003
Posts: 173
Location: Ontario, Canada
|
| Posted: Thu Dec 04, 2003 3:49 pm Post subject: |
|
|
Ahh, I never thought to do that 
Ill do it tonight, and let you know what happens.
Scott
_________________
PC: Antec 350W PSU, AMD Athlon64 3000+, ASUS K8V Deluxe Mobo, 512MB PC3200@400MHz, ATI Radeon 9800 Pro 128MB, 80GB Maxtor HDD @ 7200RPM |
|
| Back to top |
|
|
zin32
n00b
Joined: 11 Oct 2003
Posts: 14
Location: Cluj-Napoca, Romania
|
| Posted: Fri Dec 05, 2003 9:29 pm Post subject: |
|
|
I have a similar problem when emerging pykde.
My X does not restart, but my pykde won't compile.
Here's the error message.
| Code: |
make[1]: Entering directory `/var/tmp/portage/pykde-3.7.4-r2/work/PyKDE-3.7-4/kdecore'
g++ -c -pipe -w -O2 -D_REENTRANT -fPIC -DSIP_MAKE_MODULE_DLL -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -fno-exceptions -I/usr/qt/3/mkspecs/linux-g++ -I. -I../extra/kde313 -I. -I/usr/include/python2.2 -I/usr/kde/3.2/include -I/usr/qt/3/include -o kdecorehuge0.o kdecorehuge0.cpp
/usr/kde/3.2/include/kprocctrl.h: In constructor
`sipKProcessController::sipKProcessController()':
/usr/kde/3.2/include/kprocctrl.h:139: `KProcessController::KProcessController()
' is private
sipkdecoreKProcess.cpp:2001: within this context
/usr/kde/3.2/include/kprocctrl.h:140: `
KProcessController::~KProcessController()' is private
sipkdecoreKProcess.cpp:2001: within this context
/usr/kde/3.2/include/kprocctrl.h: In destructor `virtual
sipKProcessController::~sipKProcessController()':
/usr/kde/3.2/include/kprocctrl.h:140: `
KProcessController::~KProcessController()' is private
sipkdecoreKProcess.cpp:2008: within this context
/usr/kde/3.2/include/kprocctrl.h: In function `PyObject*
sipDo_KProcessController_setupHandlers(PyObject*, PyObject*)':
/usr/kde/3.2/include/kprocctrl.h:131: `static void
KProcessController::setupHandlers()' is private
sipkdecoreKProcessController.cpp:339: within this context
/usr/kde/3.2/include/kprocctrl.h: In function `PyObject*
sipDo_KProcessController_resetHandlers(PyObject*, PyObject*)':
/usr/kde/3.2/include/kprocctrl.h:132: `static void
KProcessController::resetHandlers()' is private
sipkdecoreKProcessController.cpp:362: within this context
sipkdecoreKProcessController.cpp: In function `PyObject*
sipDo_KProcessController_slotDoHousekeeping(PyObject*, PyObject*)':
sipkdecoreKProcessController.cpp:467: no matching function for call to `
KProcessController::slotDoHousekeeping(int&)'
/usr/kde/3.2/include/kprocctrl.h:120: candidates are: void
KProcessController::slotDoHousekeeping()
/usr/kde/3.2/include/kprocctrl.h: In function `void
sipDealloc_KProcessController(sipThisType*)':
/usr/kde/3.2/include/kprocctrl.h:140: `virtual
KProcessController::~KProcessController()' is private
sipkdecoreKProcessController.cpp:511: within this context
/usr/kde/3.2/include/kprocctrl.h: In function `PyObject*
sipNew_KProcessController(PyObject*, PyObject*)':
/usr/kde/3.2/include/kprocctrl.h:140: `virtual
KProcessController::~KProcessController()' is private
sipkdecoreKProcessController.cpp:564: within this context
sipkdecoreKApplication.cpp: In function `PyObject*
sipDo_KApplication_xioErrhandler(PyObject*, PyObject*)':
sipkdecoreKApplication.cpp:2620: no matching function for call to `KApplication
::xioErrhandler()'
/usr/kde/3.2/include/kapplication.h:1110: candidates are: int
KApplication::xioErrhandler(Display*)
make[1]: *** [kdecorehuge0.o] Error 1
make[1]: Leaving directory `/var/tmp/portage/pykde-3.7.4-r2/work/PyKDE-3.7-4/kdecore'
make: *** [sub-kdecore] Error 2
!!! ERROR: dev-python/pykde-3.7.4-r2 failed.
!!! Function src_compile, Line 69, Exitcode 2
!!! (no error message)
|
Also, I use kde-3.2-beta1.
--P |
|
| Back to top |
|
|
Carlo
Developer
Joined: 12 Aug 2002
Posts: 3356
|
| Posted: Fri Dec 05, 2003 10:05 pm Post subject: |
|
|
zin32: pykde is not (yet) compatible with kde 3.2.
Carlo
_________________
Please make sure that you have searched for an answer to a question after reading all the relevant docs. |
|
| Back to top |
|
|
zin32
n00b
Joined: 11 Oct 2003
Posts: 14
Location: Cluj-Napoca, Romania
|
| Posted: Fri Dec 05, 2003 11:34 pm Post subject: |
|
|
I was afraid of that 
--P |
|
| Back to top |
|
|
jeckhart
n00b
Joined: 04 Oct 2002
Posts: 6
|
| Posted: Mon Mar 15, 2004 11:13 pm Post subject: Update dependencies |
|
|
If pykde is not yet compatible with kde 3.2, shouldn't the dependencies for it be updated to reflect this? I have tried twice myself to emerge pykde to the same result. Actually, when I ran an emerge -U pykde, it wanted to UPDATE my kdelibs to 3.2.1.
Oh well, patience is a virtue. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
