Re: bash-3.2 breaks process substitution
On Wednesday 01 November 2006 19:33, Roy Marples wrote: > Repeat-By: > cat < <(ls) > /dev/fd/62: No such file or directory > > Fix: > --- execute_cmd.c 2006-11-01 18:32:36 + > +++ execute_cmd.c 2006-11-01 18:32:42 + > @@ -2672,6 +2672,7 @@ > > do_piping (pipe_in, pipe_out); > > + subshell_environment = 0; > if (async) > subshell_environment |= SUBSHELL_ASYNC; > if (pipe_in != NO_PIPE || pipe_out != NO_PIPE) > Hmmm, I just got this again with bash-3.2_p5 with the above patch. After futher review, it appears I missed another one. Attached is the patch extended a little. I can't see any more instances of this in execute_cmd.c Thanks -- Roy Marples <[EMAIL PROTECTED]> Gentoo/Linux/FreeBSD Developer (baselayout, networking) --- execute_cmd.c 2006-11-14 17:27:11 + +++ execute_cmd.c 2006-11-14 17:28:30 + @@ -2672,6 +2672,7 @@ do_piping (pipe_in, pipe_out); + subshell_environment = 0; if (async) subshell_environment |= SUBSHELL_ASYNC; if (pipe_in != NO_PIPE || pipe_out != NO_PIPE) @@ -3418,6 +3419,7 @@ /* A subshell is neither a login shell nor interactive. */ login_shell = interactive = 0; + subshell_environment = 0; if (async) subshell_environment |= SUBSHELL_ASYNC; if (pipe_in != NO_PIPE || pipe_out != NO_PIPE) ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
botched configure check for /dev/stdin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Configuration Information: Machine: i686 OS: cygwin Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' - -DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i686-pc-cygwin' -DCONF_VENDOR='pc' - -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H - -DRECYCLES_PIDS -I. -I/tmp/bash-3.2 -I/tmp/bash-3.2/include - -I/tmp/bash-3.2/lib -O2 uname output: CYGWIN_NT-5.1 LOUNGE 1.5.21(0.156/4/2) 2006-07-30 14:21 i686 Cygwin Machine Type: i686-pc-cygwin Bash Version: 3.2 Patch Level: 5 Release Status: release Description: The configure check for whether /dev/stdin is available is flawed, since it invokes 'test -r /dev/stdin /dev/stdout $ where the old bash succeeded $ echo $BASH_VERSION > /dev/stdout 3.2.1(4)-release $ Fix: Apply this patch and rerun autoconf before configuring. Using /bin/test instead of test bypasses the bash builtin, and thus bypasses an installed bash's internal special-casing of /dev/stdin. - --- aclocal.m4.orig 2006-11-15 06:35:11.78025 -0700 +++ aclocal.m4 2006-11-15 06:35:38.577125000 -0700 @@ -1574,7 +1574,7 @@ AC_CACHE_VAL(bash_cv_dev_stdin, [if test -d /dev/fd && test -r /dev/stdin < /dev/null; then bash_cv_dev_stdin=present - - elif test -d /proc/self/fd && test -r /dev/stdin < /dev/null; then + elif test -d /proc/self/fd && /bin/test -r /dev/stdin < /dev/null; then bash_cv_dev_stdin=present else bash_cv_dev_stdin=absent - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFWxmN84KuGfSFAYARAr7mAKCEtgAG/TK6A+FDJJbiju1KV3wgngCeLEZu fWLI21/shbAssMieyZo4qCo= =Yizh -END PGP SIGNATURE- ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
translations of bash, the po files
Hi, It seems that bash has never used the translations that were made at http://www.iro.umontreal.ca/translation/registry.cgi?domain=bash . At the moment Spanish and Turkish are completely up to date, and Estonian is halfway -- will these translations make it into the tarball for bash-3.3? Or what I'm really asking: if I update the Dutch translation, will it get used? And is there a publically accessible CVS or SVN repository for bash? Benno ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: botched configure check for /dev/stdin
Eric Blake wrote: > Machine Type: i686-pc-cygwin > > Bash Version: 3.2 > Patch Level: 5 > Release Status: release > > Description: > The configure check for whether /dev/stdin is available is flawed, > since it invokes 'test -r /dev/stdin configuring with a version of bash that already fakes /dev/stdin, this > means that the next configure run on bash will assume that /dev/stdin. [...] > Fix: > Apply this patch and rerun autoconf before configuring. Using > /bin/test instead of test bypasses the bash builtin, and thus bypasses an > installed bash's internal special-casing of /dev/stdin. Thanks. I've been looking at different solutions to this for a week or two. Hardcoding `/bin/test' is a tricky business: jenna.ins.cwru.edu(1)$ ls -l /bin/test /bin/ls: /bin/test: No such file or directory jenna.ins.cwru.edu(1)$ uname -a Linux jenna.ins.cwru.edu 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux Even going through a list of likely directories isn't that much better. I might end up just writing a C program to test everything. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: botched configure check for /dev/stdin
Chet Ramey <[EMAIL PROTECTED]> wrote: > Hardcoding `/bin/test' is a tricky business: How about "(exec test ...)"? Or "env test ..."? paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: translations of bash, the po files
Benno Schulenberg wrote: > Hi, > > It seems that bash has never used the translations that were made at > http://www.iro.umontreal.ca/translation/registry.cgi?domain=bash . > At the moment Spanish and Turkish are completely up to date, and > Estonian is halfway -- will these translations make it into the > tarball for bash-3.3? Or what I'm really asking: if I update the > Dutch translation, will it get used? Yes, if you update the translation, it will get used. Bash-3.2 inadvertently shipped with the bash-3.1 pot file, and I did not update it with the translation project until after 3.2 shipped. I will probably not make a bash-3.3 release, but may release the new translations in a single package before bash-4.0 comes out. > And is there a publically accessible CVS or SVN repository for bash? No. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: botched configure check for /dev/stdin
Paul Jarc wrote: > Chet Ramey <[EMAIL PROTECTED]> wrote: >> Hardcoding `/bin/test' is a tricky business: > > How about "(exec test ...)"? Or "env test ..."? Yeah, I considered the first variant. Something like (exec test -r /dev/fd/3 3http://cnswww.cns.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: translations of bash, the po files
Chet Ramey wrote: > I will probably not make a bash-3.3 release, but may release the > new translations in a single package before bash-4.0 comes out. As a separate package? Hmm, strange, but okay. If any of the strings change between 3.2 and 4.0, though, please make 4.0-pre release several weeks earlier and submit it to the TP, so the translators get a chance to catch up. Regards, Benno ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
