There are now 5 patches in: http://ftp.gnu.org/gnu/bash/bash-3.2-patches/
Maybe its worth combining them. robert On Sunday 12 November 2006 01:41, Jeremy Huntwork wrote: > Here's an interesting error. Happens in Chapter 5 Bash, when running > 'make install', using lfslivecd-x86-6.2-3 as the host: > > ( cd ./po/ ; make DESTDIR= install ) > make[1]: Entering directory `/mnt/leafos/sources/bash-3.2/po' > test -z "[EMAIL PROTECTED] [EMAIL PROTECTED] ru.gmo" || make [EMAIL PROTECTED] > [EMAIL PROTECTED] ru.gmo > make[2]: Entering directory `/mnt/leafos/sources/bash-3.2/po' > make[2]: [EMAIL PROTECTED]' is up to date. > make[2]: [EMAIL PROTECTED]' is up to date. > rm -f ru.gmo && /usr/bin/msgfmt -c --statistics -o ru.gmo ru.po > ru.po:21:9: invalid multibyte sequence > ru.po:21:10: invalid multibyte sequence > ru.po:21:11: invalid multibyte sequence > ru.po:21:12: invalid multibyte sequence > ru.po:21:13: invalid multibyte sequence > ru.po:21:14: invalid multibyte sequence > ru.po:21:15: invalid multibyte sequence > ru.po:21:16: invalid multibyte sequence > ru.po:21:17: invalid multibyte sequence > ru.po:21:18: invalid multibyte sequence > ru.po:21:19: invalid multibyte sequence > ru.po:21:20: invalid multibyte sequence > ru.po:21:22: invalid multibyte sequence > ru.po:21:23: invalid multibyte sequence > ru.po:21:24: invalid multibyte sequence > ru.po:21:25: invalid multibyte sequence > ru.po:21:26: invalid multibyte sequence > ru.po:21:27: invalid multibyte sequence > ru.po:21:29: invalid multibyte sequence > ru.po:21:30: invalid multibyte sequence > /usr/bin/msgfmt: too many errors, aborting > make[2]: *** [ru.gmo] Error 1 > > The fix is simple enough, > http://lists.gnu.org/archive/html/bug-bash/2006-10/msg00076.html > > However, I'd suggest a simple sed command instead of the patch so that > the fix isn't unnecessarily hidden. Something like: > > sed 's:UTF-8:KOI8-R:' > > -- > JH
pgpLbCyjcslOs.pgp
Description: PGP signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
