After reading your posting, I ran procsystime -a on a ./configure script out of
curiosity. Surprisingly a lot of _CPU_ time is taken by fork1. Is this the
reason why configure scripts are slow on Solaris?
(output shortened for briefness)
Elapsed Times for command ./configure,
SYSCALL
> Phil Harman wrote:
>
> > Bob Palowoda wrote:
> >
> >> There is probably nothing wrong with connection it
> just toke
> >> 123sec on a 3.2ghz machine. I just didn't wait
> long enough.
> >
> >
> >
> > Phew! 123sec is a long time. Maybe your machine was
> busy doing other stuff in the backgro
Phil Harman wrote:
> Bob Palowoda wrote:
>
>> There is probably nothing wrong with connection it just toke
>> 123sec on a 3.2ghz machine. I just didn't wait long enough.
>
>
>
> Phew! 123sec is a long time. Maybe your machine was busy doing other stuff in
> the background? Before 0.3.0 we us
