* Kyle Sallee wrote on Sat, Oct 21, 2006 at 07:52:17PM CEST:
> Okay, the 26M trace was probably typical of almost any
> of the libtool invocations during the long parts of compiling koffice.
Thanks for the trace. First, could you grab a new CVS HEAD snapshot of
Libtool (from the web page), build
Okay, the 26M trace was probably typical of almost any
of the libtool invocations during the long parts of compiling koffice.
I simply took one of the invocations of libtool I found in the compile log
and then ran it with the same shell as shown, /bin/sh
but immediately followed it with a -x and a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please keep replies on the list, so that other developers may chime in.
According to Kyle Sallee on 10/20/2006 11:53 PM:
> On 10/20/06, Eric Blake <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> According to Kyle S
Hello Kyle,
* Kyle Sallee wrote on Sat, Oct 21, 2006 at 12:48:24AM CEST:
> There was a signifigant delay between when
> I sent a request to join the list and the confirmation email.
I think there was a server outage sometime in the last couple of days.
I've discarded your earlier, pending message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Kyle Sallee on 10/20/2006 4:48 PM:
Thanks for your concerns. Yes, libtool developers are aware of the pain
of slow scripts, and have made efforts recently to speed things up, but
there are still lurking corners that could use improvement
There was a signifigant delay between when
I sent a request to join the list and the confirmation email.
Consequently, I conjectured that there would be no confirmation email.
Therefore, I sent an email to the list before confirming joining.
Consequently, I received a bounce awaiting moderator app
