[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using getconf to set max_cmd_len
From: |
Peter O'Gorman |
Subject: |
Re: Using getconf to set max_cmd_len |
Date: |
Sun, 17 Jun 2007 21:06:57 -0500 |
On Sun, 2007-06-17 at 20:39 +0200, Ralf Wildenhues wrote:
> * Charles Wilson wrote on Sun, Jun 17, 2007 at 08:32:33PM CEST:
> > OK to apply (both branches)?
>
> Of course. Thanks. And no need for my name in the ChangeLog entry.
>
> Cheers,
> Ralf
>
> > 2007-06-17 Charles Wilson <...>
> > Ralf Wildenhues <...>
> >
> > * libltdl/m4/libtool.m4 (LT_CMD_MAX_LEN): ensure error is
> > redirected even when getconf does not exist.
I noticed that when I tried this with 'getconf' changed to some
non-existing utility I got errors from expr. Turns out that we need to
quote the string for test -n.
Applied to HEAD and branch-1-5.
Peter
testquote.diff
Description: Text Data
- Re: Using getconf to set max_cmd_len, Peter O'Gorman, 2007/06/01
- Re: Using getconf to set max_cmd_len, Ralf Wildenhues, 2007/06/10
- Re: Using getconf to set max_cmd_len, Charles Wilson, 2007/06/17
- Re: Using getconf to set max_cmd_len, Ralf Wildenhues, 2007/06/17
- Re: Using getconf to set max_cmd_len, Charles Wilson, 2007/06/17
- Re: Using getconf to set max_cmd_len, Ralf Wildenhues, 2007/06/18
- Re: Using getconf to set max_cmd_len, Charles Wilson, 2007/06/18
- Re: Using getconf to set max_cmd_len, Ralf Wildenhues, 2007/06/18
- Re: Using getconf to set max_cmd_len,
Peter O'Gorman <=