Opened 16 years ago
Closed 16 years ago
#2351 closed enhancement (fixed)
Bash-4.0
Reported by: | Matthew Burgess | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.0 |
Component: | Book | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
New version. See NEWS in the tarball for details of the many changes since 3.2.
Change History (6)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
This appears to affect both libtool's and automake's test results. Libtool's failure appears to be because, at that point, its tests are invoked via /tools/bin/bash. When it tries to do 'LC_ALL=de_DE' it fails with:
bash: warning: setlocale: LC_ALL: cannot change locale (de_DE): No such file or directory.
I've worked around this in my current builds by moving readline and bash to just before libtool so that bash is linked against /lib/libc.so.6, which has the locales installed, as opposed to /tools/lib/libc.so.6, which doesn't.
I'd appreciate it if someone could confirm the workaroud is the right fix, or whether this appears to be an undesired change in Bash-4.0.
As for the automake test, I can't figure out what the failing test, check10.test, is actually trying to do. If someone could distill this into a simple (to invoke) shell script please, I'll see if I can figure out why bash-4.0 apparently isn't playing nicely.
comment:3 by , 16 years ago
Having taken a proper look, I've now figured out what the test is doing and how it works (must've been bleary eyed in comment:2:ticket:2351). The following is enough to trigger the fault without having to wait for the ridiculously long test suite to run:
make TESTS=check10.test check
Once my current rebuild, including coreutils-7.1, has finished/failed at this point, I'll see if I can figure out what's going on. Obviously, if anyone else gets to this point before me, feel free to let us know how you get on :-)
comment:4 by , 16 years ago
The automake failure is known upstream and http://git.savannah.gnu.org/cgit/automake.git/diff/?id=f51165dd1a6ca52d64ba73697e9ba4a24715b0ec may well fix it. Apparently, originally triggered under ksh, bash-4.0 may well be triggering it now.
comment:5 by , 16 years ago
Sure enough, that upstream automake patch fixes the test failure. An LFS-style patch has been committed at http://wiki.linuxfromscratch.org/patches/browser/trunk/automake/automake-1.10.2-test_fix-1.patch.
The bash-4.0 tarball now includes all the documentation, so the separate -doc tarball can be dropped from the book.