Summary: | kbuildsycoca4 fails after compiling kdebase on Windows with emerge tool | ||
---|---|---|---|
Product: | kde-windows | Reporter: | Christoph Watzl <christoph.watzl> |
Component: | buildsystem | Assignee: | Christian Ehrlicher <Ch.Ehrlicher> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Verbose task list ('tasklist /v') |
Description
Christoph Watzl
2008-02-08 15:25:08 UTC
did you run kbuildsycoca4 with all kde processes shut down? otherwise it doesn't get a lock. Created attachment 23479 [details]
Verbose task list ('tasklist /v')
Oops, I meant to write a comment to the above attachment - well, killing all processes that didn't seem important didn't help. In the attachment of the previous comment is the list of all processes I had running. Just some additional info that I forgot: I'm running Windows XP Professional 32-bit on an Intel Core 2 Duo processor, and I'm using an account with administrator privileges (I know how that sucks :-)). Sorry, can't reproduce it on a clean win xp with mingw. You're using mingw, right? Do you maybe use your own mingw installation instead the one from emerge? Please rebuild dbus with emerge: emerge dbus-src and try again. w00t! Now it works! Actually, I had an old standalone MinGW installation which I've been using with eclipse CDT in the past - this may have caused some kind of conflict with the MinGW installation that was installed via emerge. So I uninstalled the old MinGW and did 'emerge dbus-src' as you suggested; afterwards everything worked fine. The sad thing is that I can't tell which of the two steps was actually necessary ... Anyway, thanks for your patience with me! :-) Fne that it works now but it doesn't solve our problem - you're now using a self - compiled dbus instead our binaries. That's fine for you but isn't manageable for all :) Is it possible to do some debug testing on your system? If yes, let me know. Thx Another question. Was C:\KDE\bin\dbus-daemon.exe available before you installed dbus-src ? As for your second question: I can't really tell, now that it's there, but I could try it again with a clean installation. This will, of course, take some time. :-) And to your first question: Sure, I have a lot of time at the moment. Feel free to e-mail me at any time (BTW, I'm German speaking :-)). After doing a clean rebuild of everything (I deleted my old KDE directory), I couldn't reproduce the problem any more. I really can't tell what the trouble was. I think we found the problem: There was an error in our win32libs python script to install also msvc libs. This was fixed recently --> svn up emerge emerge --unmerge dbus-src --unmerge win32libs emerge win32libs |