Hi,

I managed to build it after upgrading to mandrakes newest RPMs, thanks 
for the info Mario and Amilcar.

I do however have another really strange problem. I've had it pretty 
much since I started using the betas for 3.2 of KDE. I'm not blaming 
kdevelop but it affects kdevelop badly.

When I start kdevelop in a directory it outputs alot of stuff, in the 
end it start iterating over the files (apparently failing in some way) 
in the dir I started it, e.g:

kio (KIOJob): stat file:/home/ddskrjo/dev/sandbox/CCA/tags
kio (Slave): slave failed to connect to application pid=29222
protocol=thumbnail
kio (Slave): Houston, we lost our slave, pid=29222
kio (Slave): slave died pid = 29222

When it is done with that kdevelop dies, I'm unable to get a backtrace 
of it.

If I load a project before this "countdown" has finished, it has 
happened that kdeveloped has stayed alive, but most of the times it 
crashes similarily.

However, If I immediately start a new project, importing the one I was 
working on, kdevelop stays alive. (!)
The errors like above still appear but they are no longer fatal.

Has anyone else seen this, or something similar? It drives me nuts ;).

Regards,
Robert

Mario Scalas wrote:
> On Monday 08 December 2003 15:37, Robert Jonsson wrote:
> 
>>Hi,
>>
>>I've had this error for several days now trying to compile a daily cvs
>>checkout. Anyone know if there is something in progress or my system thats
>>faulty?
>>
>>Using KDE3.1.93, gcc 3.3.1
>>---------
> 
> 
> Same here: you need to update your kde to a recent cvs or at least kde 3.2 
> beta2.
> 
> 
>>/Robert
>>
>>_______________________________________________
>>Kdevelop-devel mailing list
>>Kdevelop-devel@barney.cs.uni-potsdam.de
>>http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
> 
> 


_______________________________________________
Kdevelop-devel mailing list
Kdevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel