On Mon, Feb 15, 2016 at 04:07:58PM -0600, Bruce Dubbs wrote:
> 
> I do subscribe to the grep mailing list.  There was a change in 2.23 that
> IIRC was related to this.  What I see as the problem is the line:
> 
> /usr/share/doc/kbd-2.0.3/utf/<E2><99><AA><E2><99><AC>

Yes, I noticed that, but compared to the more urgent problem it
seemed unimportant.  <sigh/>
> 
> What happens if you prefix your grep commands with LC_ALL=en_US.utf8?
> Or the GB equivalent.
> 

Seems to work for me.  So 'grep -v' in the C or POSIX locales is
failing badly, but ok in utf8 locales.

Possibly from that UTF-8 kbd file.  If I only run it in e.g. /bin
the C version works fine, so it seems that it falls over at
characters which cannot be correctly processed in the current
locale.

>/tmp/list003-utf
> What I get is:
> 
> $ ls /usr/share/doc/kbd-2.0.3/utf | grep -v utf
> README
> ethiopic
> Binary file (standard input) matches
> 
> $ ls /usr/share/doc/kbd-2.0.3/utf | LC_ALL=en_US.utf8 grep -v utf
> README
> ethiopic
> ♪♬

Good job we are using graphical terms, I don't think most console
fonts include musical notes.

# ls /usr/share/doc/kbd-2.0.3/utf/
README  ethiopic  utfdemo  utflist  ''$'\342\231\252\342\231\254'

Interestingly, my log from the build using LFS at 2nd February with
the default environment shows that same file as being installed:

/usr/share/doc/kbd-2.0.3/utf
/usr/share/doc/kbd-2.0.3/utf/README
/usr/share/doc/kbd-2.0.3/utf/ethiopic
/usr/share/doc/kbd-2.0.3/utf/utfdemo
/usr/share/doc/kbd-2.0.3/utf/utflist
/usr/share/doc/kbd-2.0.3/utf/♪♬
/usr/share/keymaps

I will note that after listing all the files (I separately list
directories, and /opt/texinfo  [ on old builds that was a separate
filesystem ] I sort them and have been using LC_ALL=C for the sort.

My logs from gzip and iproute2 are correct, so it was indeed kbd
which broke my logging with this version of grep.

ĸen
-- 
This email was written using 100% recycled letters.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to