Re: Using getconf to set max_cmd_len

* Charles Wilson wrote on Mon, Jun 18, 2007 at 02:21:30PM CEST: > Ralf Wildenhues wrote: > >* Charles Wilson wrote on Sun, Jun 17, 2007 at 10:20:24PM CEST: > >>Committed (to HEAD and branch-1-5). my sendmail hiccuped when trying to > >>send the notification to libtool-commit for branch-1-5, thoug

Re: Using getconf to set max_cmd_len

Ralf Wildenhues wrote: * Charles Wilson wrote on Sun, Jun 17, 2007 at 10:20:24PM CEST: Committed (to HEAD and branch-1-5). my sendmail hiccuped when trying to send the notification to libtool-commit for branch-1-5, though. I can try to reconstruct that message manually and send it, if you thi

Re: Using getconf to set max_cmd_len

Hi Charles, * Charles Wilson wrote on Sun, Jun 17, 2007 at 10:20:24PM CEST: > > Committed (to HEAD and branch-1-5). my sendmail hiccuped when trying to > send the notification to libtool-commit for branch-1-5, though. I can > try to reconstruct that message manually and send it, if you think

Re: Using getconf to set max_cmd_len

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 <...> > >

Re: Using getconf to set max_cmd_len

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/li

Re: Using getconf to set max_cmd_len

* 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

Re: Using getconf to set max_cmd_len

Ralf Wildenhues wrote: * Steve Ellcey wrote on Thu, May 31, 2007 at 12:58:37AM CEST: 2007-05-30 Steve Ellcey <[EMAIL PROTECTED]> * libltdl/m4/libtool.m4 (LT_CMD_MAX_LEN): Try using getconf to set lt_cv_sys_max_cmd_len. [...] +lt_cv_sys_max_cmd_len=`getconf ARG_MAX 2> /d

Re: Using getconf to set max_cmd_len

* Steve Ellcey wrote on Thu, May 31, 2007 at 12:58:37AM CEST: > 2007-05-30 Steve Ellcey <[EMAIL PROTECTED]> > > * libltdl/m4/libtool.m4 (LT_CMD_MAX_LEN): Try using getconf > to set lt_cv_sys_max_cmd_len. [...] > +lt_cv_sys_max_cmd_len=`getconf ARG_MAX 2> /dev/null` The patch

Re: Using getconf to set max_cmd_len

On Thu, 2007-05-31 at 08:08 +0200, Paolo Bonzini wrote: > Steve Ellcey wrote: > > While integrating a newer libtool into GCC, an issue arose with what > > value libtool was setting max_cmd_len to. This patch uses 'getconf > > ARG_MAX' to set lt_cv_sys_max_cmd_len instead of going through a loop to

Re: Using getconf to set max_cmd_len

Steve Ellcey wrote: While integrating a newer libtool into GCC, an issue arose with what value libtool was setting max_cmd_len to. This patch uses 'getconf ARG_MAX' to set lt_cv_sys_max_cmd_len instead of going through a loop to try and divine the right value, this should give a more accurate va

Re: Using getconf to set max_cmd_len

On Wed, 2007-05-30 at 15:58 -0700, Steve Ellcey wrote: > While integrating a newer libtool into GCC, an issue arose with what > value libtool was setting max_cmd_len to. This patch uses 'getconf > ARG_MAX' to set lt_cv_sys_max_cmd_len instead of going through a loop to > try and divine the right v

Using getconf to set max_cmd_len

While integrating a newer libtool into GCC, an issue arose with what value libtool was setting max_cmd_len to. This patch uses 'getconf ARG_MAX' to set lt_cv_sys_max_cmd_len instead of going through a loop to try and divine the right value, this should give a more accurate value and should be fast