Hello Chet,
* Chet Ramey wrote on Mon, Jan 31, 2011 at 04:37:32PM CET:
> On 1/30/11 3:50 AM, Ralf Wildenhues wrote:
> >> On Sat, Jan 29, 2011 at 5:58 PM, Chet Ramey wrote:
> >>> On 1/25/11 10:08 PM, Peter O'Gorman wrote:
> for lt_wr_arg
> do
> case \$lt_wr_arg in
>
On Sat, Jan 29, 2011 at 5:58 PM, Chet Ramey wrote:
> On 1/25/11 10:08 PM, Peter O'Gorman wrote:
>> Hi,
>>
>> Dan reported a libtool performance regression in libtool-2.4 when running
>> his binaries with a large number of arguments.
>>
>> Libtool creates a shell script which usually sets some env
On 1/30/11 3:50 AM, Ralf Wildenhues wrote:
> Hello,
>
> * Dan McGee wrote on Sun, Jan 30, 2011 at 01:04:17AM CET:
>> On Sat, Jan 29, 2011 at 5:58 PM, Chet Ramey wrote:
>>> On 1/25/11 10:08 PM, Peter O'Gorman wrote:
for lt_wr_arg
do
case \$lt_wr_arg in
--lt-*) ;;
>>
Hello,
* Dan McGee wrote on Sun, Jan 30, 2011 at 01:04:17AM CET:
> On Sat, Jan 29, 2011 at 5:58 PM, Chet Ramey wrote:
> > On 1/25/11 10:08 PM, Peter O'Gorman wrote:
> >> for lt_wr_arg
> >> do
> >> case \$lt_wr_arg in
> >> --lt-*) ;;
> >> *) set x "$@" "$lt_wr_arg"; shift;;
> >>
On 1/25/11 10:08 PM, Peter O'Gorman wrote:
> Hi,
>
> Dan reported a libtool performance regression in libtool-2.4 when running
> his binaries with a large number of arguments.
>
> Libtool creates a shell script which usually sets some env vars and runs
> the binary, new in recent libtool, the scr
Hi,
Dan reported a libtool performance regression in libtool-2.4 when
running his binaries with a large number of arguments.
Libtool creates a shell script which usually sets some env vars and runs
the binary, new in recent libtool, the script also takes arguments, so
these have to be remove
