GCC 3.1 - even slower compilation and relocation

[Lubos Lunak]

On Sunday 19 May 2002 21:09, Piotr Szymanski wrote:
> Hi,
>
> Once on a beatiful day Sunday 19 May 2002 18:44, Bernhard Rosenkraenzer 
wrote:
> > Better yet, use prelink, it's a much cleaner solution.
>
> What is  prelink and how does it differ from objprelink?
>
> > > exchange kdebase's startkde with startkde from:
> > > http://www.kde-look.org/content/files/1332-startup.tar.gz
> >
> > Don't. Read the script in there. It's broken, and actually decreases
> > startup time by failing to initialize things (due to the missing kdeinit
> > stuff, application startup will take much longer with that script).
>
> It is broken, so do not use it, unless you want to test it, but that is not
> supported, but it certainly does not make apps load slower, in fact it does
> the opposite. My kde starts much faster when using this script, in fact the
> script from KDE_3_0_1_RELEASE is very slow, it takes over one and a half
> minute to load.

 Even my K6/188 at home doesn't need that much time, not even half.

> I have been using this new script and it starts in 15
> seconds and konqueror starts like ie in windows (circa 4 sec.), but when
> using kdebase's startkdei takes at least 45 sec. I have completely no idea

 Hmms. I'd have to take out some of the RAM chips from the home computer or 
make it very busy in order to start Konqy for that long.

> why this is, but it is that whay.

 Whatever it is, something is broken with your setup. Which also means that 
with normal non-broken ones, the modified startkde script can make no 
different or can make things even worse (but that's just a possibility, I 
can't check myself before I get home). You could probably try modifying the 
original startkde script as I already said to find out what exactly is the 
change that makes so big difference.

-- 
 Lubos Lunak
 l.lunak at email.cz ; l.lunak at kde.org
 http://dforce.sh.cvut.cz/~seli