> I'm trying to build Bash 3.1 on Wndows XP system using MSYS. I'm getting a
> build failure at make as follows:
Sorry, I don't really support Windows. I generally steer folks to cygwin
if they want to run bash on Windows. I think the mingw32 folks have bash
patches available, too.
Chet
--
``
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(
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.
Thanks for pointing this out. This would indeed be a significant
improvement!
Alex Howells wrote:
> 2009/2/2 Chet Ramey :
>> 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
Nicolas 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 figur
2009/2/2 Chet Ramey :
> 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
a...@howells.me wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i486
> OS: linux-gnu
> Compiler: gcc
>
> Description:
> http://pastebin.com/f476b80da
> configured via: http://pastebin.com/m62b92718
>
> Adding --enable-minimal doesn't fix t
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 proble
