Gary V. Vaughan skrev 2011-11-25 09:57:
> Determine, on a function by function basis, what XSI features
> are available in the shell that is actually running the script,
> rather than the one that was picked at configure time by the
> re-execution engine.
Doesn't this mean that the libtool script
Hi Peter,
On 28 Nov 2011, at 15:48, Peter Rosin wrote:
> Gary V. Vaughan skrev 2011-11-25 09:57:
>> Determine, on a function by function basis, what XSI features
>> are available in the shell that is actually running the script,
>> rather than the one that was picked at configure time by the
>> re
Gary V. Vaughan skrev 2011-11-28 10:20:
> Hi Peter,
>
> On 28 Nov 2011, at 15:48, Peter Rosin wrote:
>> Gary V. Vaughan skrev 2011-11-25 09:57:
>>> Determine, on a function by function basis, what XSI features
>>> are available in the shell that is actually running the script,
>>> rather than the
Hi Peter,
On 28 Nov 2011, at 18:05, Peter Rosin wrote:
> Gary V. Vaughan skrev 2011-11-28 10:20:
>> On 28 Nov 2011, at 15:48, Peter Rosin wrote:
>>> Gary V. Vaughan skrev 2011-11-25 09:57:
Determine, on a function by function basis, what XSI features
are available in the shell that is ac
On Mon, 28 Nov 2011, Peter Rosin wrote:
My typical use case is "mid-sized" at a magnitude or so larger, and
even there with a fork rate of approx 10-15 Hz as I'm seeing, it wouldn't
be too harsh with a couple of extra forks - a minutes or so on the
wall clock time. But it would really add to the
On 11/25/2011 11:57 PM, Gary V. Vaughan wrote:
> On 26 Nov 2011, at 11:39, Charles Wilson wrote:
>> a) This is a big holiday weekend in the US, so...a bit more than 72
>> hours is indicated. Most of us will still be catching up on
>> post-holiday $realjob stuff by the time 72 hours expires.
>
> A
