Testing last week's -svn (everything except glibc-2.19 : if _that_
causes problems, I'd like to correctly attribute the blame).  Got a
test failure in man-db :

root in chroot /# cat
/building/man-db-2.6.6/src/tests/test-suite.log 
============================================
   man-db 2.6.6: src/tests/test-suite.log
============================================

# TOTAL: 21
# PASS:  20
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: man-6
===========

col: Invalid or incomplete multibyte or wide character
/building/man-db-2.6.6/src/.libs/lt-man: command exited with status
1: LC_CTYPE=en_US.UTF-8 col -b -p -x
  FAIL: missing locales

root in chroot /# LC_ALL=en_US.UTF-8
bash: warning: setlocale: LC_ALL: cannot change locale
(en_US.UTF-8): No such file or directory
root in chroot /# LC_ALL=en_GB.UTF-8
bash: warning: setlocale: LC_ALL: cannot change locale
(en_GB.UTF-8): No such file or directory
root in chroot /# LC_ALL=C
root in chroot /#

 I haven't seen this failure before.

 Snippets from the glibc log :

make[2]: Entering directory '/building/glibc-2.18/localedata'
.././scripts/mkinstalldirs /usr/lib/locale
mkdir -p -- /usr/lib/locale
aa_DJ.UTF-8... done
aa_DJ.ISO-8859-1... done
...
en_DK.UTF-8... done
en_DK.ISO-8859-1... done
en_GB.UTF-8... done
en_GB.ISO-8859-1... done
en_HK.UTF-8... done
en_HK.ISO-8859-1... done
en_IE.UTF-8... done
en_IE.ISO-8859-1... done
en_IE.ISO-8859-15@euro... done
en_IN.UTF-8... done
en_NG.UTF-8... done
en_NZ.UTF-8... done
en_NZ.ISO-8859-1... done
en_PH.UTF-8... done
en_PH.ISO-8859-1... done
en_SG.UTF-8... done
en_SG.ISO-8859-1... done
en_US.UTF-8... done
en_US.ISO-8859-1... done
en_ZA.UTF-8... done
...

 Will use make -k check in my build, and carry on.  Again, probably
a new issue that only applies to my builds.  Will be interested to
see how it looks when booted.

ĸen
-- 
das eine Mal als Tragödie, dieses Mal als Farce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to