On Mon, May 04, 2020 at 12:50:12PM +0800, Xi Ruoyao via lfs-dev wrote:
> On 2020-05-04 04:12 +0100,Ken Moffat via lfs-dev wrote:
> > On Mon, May 04, 2020 at 03:34:53AM +0100, Ken Moffat via lfs-dev wrote:
> > > On Mon, May 04, 2020 at 09:53:04AM +0800, Xi Ruoyao via lfs-dev wrote:
> > > > On 2020-05-04 02:15 +0100, Ken Moffat via lfs-dev wrote:
> > > > > On Sun, May 03, 2020 at 04:18:57AM +0100, Ken Moffat via lfs-dev 
> > > > > wrote:
> > > > > > I'm building with LFS as at 25th April.  My previous build was in
> > > > > > early April, and I think this is the first time I've seen a failure
> > > > > > in the man-db tests.  With man-db-2.9.1 :
> > > > > > 
> > > > > > FAIL: man-missing-locales
> > > > > > 
> > > > > > and src/tests/test-suite.log has:
> > > > > > 
> > > > > > FAIL: man-missing-locales     
> > > > > > =========================
> > > > > > 
> > > > > > col: failed on line 319: Invalid or incomplete multibyte or wide
> > > > > > character
> > > > > > man: command exited with status 127: LC_CTYPE=en_US.UTF-8 col -b -p 
> > > > > > -x
> > > > > > | sed
> > > > > > -e '/^[[:space:]]*$/{ N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> > > > > >   FAIL: missing locales
> > > > > > FAIL man-missing-locales (exit status: 1)
> > > > > > 
> > > > > > Given that things have changed since my previous build, is anyone
> > > > > > else seeing this ?  I suspect the error might be "mine, all mine",
> > > > > > so I'm reluctant to add to the noise by reporting iti upstream
> > > > > > unless it really is common.  Looking at my glibc log I did
> > > > > > apparently install the en_US.UTF-8 locale.
> > > > > > 
> > > > > > ĸen
> > > > > 
> > > > > Update: I'm doing a fresh build to look at the test failures in this
> > > > > and in bison (and also to make sure I've fixed my own screw-up in
> > > > > removing the symlinked headers before rebuilding util-linux).
> > > > > 
> > > > > Got to bison, failures as before.  First is
> > > > > 
> > > > > 131. diagnostics.at:107: testing Warnings ...
> > > > > ./diagnostics.at:107: LC_ALL="$locale"  bison -fcaret --color=debug
> > > > > -Wall
> > > > > input.y
> > > > > --- experr      2020-05-03 23:20:06.028040360 +0000
> > > > > +++ /building/bison-3.5.4/tests/testsuite.dir/at-
> > > > > groups/131/stderr      2020-
> > > > > 05-03 23:20:06.057040734 +0000
> > > > > @@ -1,3 +1,4 @@
> > > > > +/bin/sh: warning: setlocale: LC_ALL: cannot change locale 
> > > > > (en_US.utf8)
> > > > >  input.y:9.12-14: <warning>warning:</warning> symbol FOO redeclared
> > > > > [<warning>-Wother</warning>]
> > > > >      9 | %token FOO <warning>FOO</warning> FOO
> > > > >        |            <warning>^~~</warning>
> > > > > 131. diagnostics.at:107: 131. Warnings (diagnostics.at:107): FAILED
> > > > > (diagnostics.at:107)
> > > > > 
> > > > > So, bothi bison and man-db test failures are for en_US.{UTF-8,utf8}
> > > > > variants.  The capitalized version is definitely installed, accoding
> > > > > to my log from glibc.
> > > > 
> > > > So I think the issue is: we are using chapter 5 bash for bison, and
> > > > chapter 5
> > > > util-linux for man-db.  Chapter 5 tools' locale archive is
> > > > /tools/lib/locale/locale-archive, which is not installed.
> > > > 
> > > > Maybe installing en_US.UTF-8 locale in chap. 5 glibc would solve this
> > > > problem.
> > > > -- 
> > > > Xi Ruoyao <xry...@mengyan1223.wang>
> > > > School of Aerospace Science and Technology, Xidian University
> > > > 
> > > 
> > > Sounds plausible.  Will give it a try.
> > > 
> > > ĸen
> > 
> > Came back to it to check that glibc had got through my additions,
> > then checked the logs.  In all three runs glibc seems to have
> > installed a LOT of locales in /tools/hare/i18n/locales/
> 
> They are "uncompiled" locale data.  Use:
> 
> install -vdm755 /tools/lib/locale
> /tools/bin/localedef -i en_US -f UTF-8 en_US.UTF-8
> 
> to make a /tools/bin/locale/locale-archive (which is necessary at runtime, to
> use locales) from them.
> 

What I added after make install was:

mkdir -pv /tools/lib/locale
localedef -i en_US -f UTF-8 en_GB.UTF-8

And since I was running as the lfs user, I don't think using a path
on localedef is necessary.

> > No longer hopeful, but will let it run.
> > 

13 failures, as before.

ĸen
-- 
                 See You Later, Holy Poppadom!
                    -- Red Dwarf, The Promised Land
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to