GNU bug report logs - #18906
2.4.3: fix for loop

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Arkadiusz Miśkiewicz <arekm <at> maven.pl>
Subject: bug#18906: closed (Re: bug#18906: 2.4.3: fix for loop)
Date: Sun, 02 Nov 2014 17:49:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#18906: 2.4.3: fix for loop

which was filed against the libtool package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 18906 <at> debbugs.gnu.org.

-- 
18906: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18906
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: "Gary V. Vaughan" <gary <at> vaughan.pe>
To: Arkadiusz Miśkiewicz <arekm <at> maven.pl>
Cc: 18906-close <at> debbugs.gnu.org
Subject: Re: bug#18906: 2.4.3: fix for loop
Date: Sun, 2 Nov 2014 17:48:36 +0000

Hi Arkadiusz,

> On Oct 30, 2014, at 10:29 PM, Arkadiusz Miśkiewicz <arekm <at> maven.pl> wrote:
> 
> 
> Fix for loop in cmdline_wrap test.
> 
> --- libtool-2.4.3/tests/cmdline_wrap.at~	2014-10-27 18:20:51.000000000 +0100
> +++ libtool-2.4.3/tests/cmdline_wrap.at	2014-10-30 22:37:17.938397654 +0100
> @@ -28,7 +28,7 @@
> AT_SETUP([Run tests with low max_cmd_len])
> AT_KEYWORDS([recursive expensive])
> dnl If we already have failures, then reruns will fail too!
> -fail_list=`for f in ?/fail ??/fail ???/fail ????/fail; do echo $f; end`
> +fail_list=`for f in ?/fail ??/fail ???/fail ????/fail; do echo $f; done`
> AT_CHECK([test -z "$fail_list" || (exit 77)])
> m4_ifdef([AT_CAPTURE_FILE],
> [AT_CAPTURE_FILE([testsuite.log])])

Nice catch!  I was wondering why that wasn't working, and hadn't had the time to
look.

Applied and pushed.

Cheers,
-- 
Gary V. Vaughan (gary AT gnu DOT org)

[Message part 3 (message/rfc822, inline)]

From: Arkadiusz Miśkiewicz <arekm <at> maven.pl>
To: bug-libtool <at> gnu.org
Subject: 2.4.3: fix for loop
Date: Thu, 30 Oct 2014 23:29:56 +0100

Fix for loop in cmdline_wrap test.

--- libtool-2.4.3/tests/cmdline_wrap.at~	2014-10-27 18:20:51.000000000 +0100
+++ libtool-2.4.3/tests/cmdline_wrap.at	2014-10-30 22:37:17.938397654 +0100
@@ -28,7 +28,7 @@
 AT_SETUP([Run tests with low max_cmd_len])
 AT_KEYWORDS([recursive expensive])
 dnl If we already have failures, then reruns will fail too!
-fail_list=`for f in ?/fail ??/fail ???/fail ????/fail; do echo $f; end`
+fail_list=`for f in ?/fail ??/fail ???/fail ????/fail; do echo $f; done`
 AT_CHECK([test -z "$fail_list" || (exit 77)])
 m4_ifdef([AT_CAPTURE_FILE],
 [AT_CAPTURE_FILE([testsuite.log])])

-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.