Okay, I have absolutely no idea how the two things are related, but I have tried and retried for confirmation and it keeps happening.
Currently, OLAD has gotten pretty big, fpc tells me it's compiling 15442 lines to build (it was actually over 19 000 earlier today but I've spent most of the day doing code cleanups). Now, after building, you see it linking. This takes a while. My current setup is lazarus running as a GTK1.2 app, compiling OLAD as a GTK2 app, but using the GTK2 IDE didn't affect these results. Start the IDE with command ./lazarus: link time approximately 2 minutes, Start tthe IDE with command ./startlazarus: link time ranging between 30 and 45 minutes (I am not making this up !). Even the 2 mins is a LOT since nothing else is that slow, but I know lazarus/fpc links differently due to the pascal model and for the rest of it I'm willing to live with that, according to PS, ld is in an uninteruptable sleep, waiting for IO. These results are with lazarus from subversion built last night. Interestingly, while linking the rest of the computer becomes pretty much unusable, I suspect my laptop's drive is not of the fastest and this is what slows down ld, which in turn ties up the system . What I don't get is why running startlazarus would have such a massive impact on these IO times ? I'll be happy to provide whatever information could help solve it. PS. In both cases I'm runing lazarus from an install in ~/lazarus/ Ciao A.J. -- A.J. Venter Chief Software Architect OpenLab International http://www.getopenlab.com http://www.silentcoder.co.za _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
