Re: Bash-4.0-rc1 available for FTP
Nicolas niko...@gmail.com writes: Hello, I ran some benchmarks of Bash 4.0-rc1. It is quite impressive! Here are the results. My computer is a Pentium M (running at 600 MHz for the test), running Linux 2.6.26 with libc6 version 2.7 and Debian bash-completion version 20080705. The figures are averages over 100 tests. Bash 3.2, without bash malloc: * eval `dircolors`: 0.636s * source /etc/bash_completion: 0.721s Bash 4.0, with bash malloc: * eval `dircolors`: 0.385s * source /etc/bash_completion: 41.651s (around 93% of the time is spent in function find_entry of lib/malloc/table.c) Bash 4.0, without bash malloc: * eval `dircolors`: 0.132s * source /etc/bash_completion: 0.703s bash_completion is too slow because it does strange things: it parses itself because it wants to emulate the behavior of -o plusdirs. See https://bugzilla.redhat.com/show_bug.cgi?id=479936 for a preliminary patch.
Re: bash 3.2 and bash 4.0 (RC1) fail to build statically
2009/2/2 Chet Ramey chet.ra...@case.edu: I was able to successfully compile and link after configuring --enable-static-link --without-bash-malloc (there's some problem with libc and the bash malloc when you try a static link). Yep that works for me too on anything except Debian GNU/Linux. On that I get failure to link. If I figure out what's wrong in that specific case I'll let you know =) For now it builds just fine on F10 (32-bit and 64-bit) as well as Gentoo Linux (32-bit and 64-bit) which is sufficient. Cheers for the response. Much appreciated. Alex
Build Problem
Hello, I'm trying to build Bash 3.1 on Wndows XP system using MSYS. I'm getting a build failure at make as follows: *** *** * * * GNU bash, version 3.1.0(1)-release (i686-pc-mingw32) * * *** rm -f shell.o gcc -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='mingw32' - DCONF_MACHTYPE='i686-pc-mingw32' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -I./lib/intl -I/c/bash-3.1/lib/intl -g -O2 -c shell.c shell.c:40:17: pwd.h: No such file or directory In file included from shell.h:42, from shell.c:50: externs.h:172: error: conflicting types for 'getcwd' c:/mingw/bin/../lib/gcc/mingw32/3.4.5/../../../../include/io.h:175: error: previous declaration of 'getcwd' was here externs.h:172: error: conflicting types for 'getcwd' c:/mingw/bin/../lib/gcc/mingw32/3.4.5/../../../../include/io.h:175: error: previous declaration of 'getcwd' was here shell.c: In function `open_shell_script': shell.c:1436: error: `F_SETFD' undeclared (first use in this function) shell.c:1436: error: (Each undeclared identifier is reported only once shell.c:1436: error: for each function it appears in.) shell.c: In function `get_current_user_info': shell.c:1590: error: dereferencing pointer to incomplete type shell.c:1590: error: dereferencing pointer to incomplete type shell.c:1591: error: dereferencing pointer to incomplete type shell.c:1591: error: dereferencing pointer to incomplete type shell.c:1592: error: dereferencing pointer to incomplete type shell.c:1592: error: dereferencing pointer to incomplete type shell.c:1594: error: dereferencing pointer to incomplete type shell.c:1594: error: dereferencing pointer to incomplete type make: *** [shell.o] Error 1 Kindly Help Rupinder
Re: bash, no slash
Hi Chet I'm almost positive that you've remapped / to another character (or a command that has no discernible effect) in readline. Look at your readline startup files. You can see your current key bindings with `bind -p' from the bash prompt. thanks, I was finally able to find the problem. it was a faulty line in inputrc. I have no idea why I was trying to source /etc/bash.bashrc from inputrc (probably was following some guide and typed that line in the wrong file). So the line was interpreted as a remap of '/'. thanks again regards, davide
Re: bash 3.2 and bash 4.0 (RC1) fail to build statically
Alex Howells wrote: 2009/2/2 Chet Ramey chet.ra...@case.edu: I was able to successfully compile and link after configuring --enable-static-link --without-bash-malloc (there's some problem with libc and the bash malloc when you try a static link). Yep that works for me too on anything except Debian GNU/Linux. On that I get failure to link. My results were for Debian (lenny/sid). Sorry that I didn't state that explicitly. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
