[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: testsuite -C dir

From: Eric Blake
Subject: Re: testsuite -C dir
Date: Tue, 29 Jan 2008 07:46:04 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20071031 Thunderbird/ Mnenhy/

Hash: SHA1

According to Eric Blake on 1/29/2008 7:31 AM:
| Hmm.  Bash explicitly documents that it behaves differently depending on
| whether it is in POSIX mode - from bash-3.2/POSIX:
| ~ 28. The `.' and `source' builtins do not search the current directory
| ~     for the filename argument if it is not found by searching `PATH'.
| It looks like we've discovered a bash bug.

In my tests, ksh and zsh were okay, but the version of ash available on
cygwin also had the bug.  So I'm adding this to the manual:

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at
Comment: Using GnuPG with Mozilla -

>From 9935105de6e18dba029660d60f42b8b81d7ac3c4 Mon Sep 17 00:00:00 2001
From: Eric Blake <address@hidden>
Date: Tue, 29 Jan 2008 07:45:10 -0700
Subject: [PATCH] * doc/autoconf.texi (Limitations of Builtins) <.>: Mention 
bash bug.

Signed-off-by: Eric Blake <address@hidden>
 ChangeLog         |    5 +++++
 doc/autoconf.texi |   10 ++++++----
 2 files changed, 11 insertions(+), 4 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 42da03c..8d592df 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2008-01-29  Eric Blake  <address@hidden>
+       * doc/autoconf.texi (Limitations of Builtins) <.>: Mention bash
+       bug.
 2008-01-28  Eric Blake  <address@hidden>
        Fix regression in handling VAR=VALUE arguments to testsuite.
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index f6421d7..9c5b192 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -13598,10 +13598,12 @@ the @samp{x} into account later in the pipe.
 @c --------------
 @prindex @command{.}
 Use @command{.} only with regular files (use @samp{test -f}).  Bash
-2.03, for instance, chokes on @samp{. /dev/null}.  Also, remember that
address@hidden uses @env{PATH} if its argument contains no slashes, so if
-you want to use @command{.} on a file @file{foo} in the current
-directory, you must use @samp{. ./foo}.
+2.03, for instance, chokes on @samp{. /dev/null}.  Remember that
address@hidden uses @env{PATH} if its argument contains no slashes.  Also,
+some shells, including bash 3.2, implicitly append the current directory
+to this @env{PATH} search, even though Posix forbids it.  So if you want
+to use @command{.} on a file @file{foo} in the current directory, you
+must use @samp{. ./foo}.
 @item @command{!}
 @c --------------

reply via email to

[Prev in Thread] Current Thread [Next in Thread]