Seems like it is a locale issue: # grep locale testsuite.dir/*/testsuite.log
testsuite.dir/130/testsuite.log:./diagnostics.at:107: LC_ALL="$locale" bison -fcaret --color=debug -Wall input.y testsuite.dir/130/testsuite.log:+/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/131/testsuite.log:./diagnostics.at:152: LC_ALL="$locale" bison -fcaret --color=debug -Wall input.y testsuite.dir/131/testsuite.log:+/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/132/testsuite.log:./diagnostics.at:208: LC_ALL="$locale" bison -fcaret --color=debug -Wall input.y testsuite.dir/132/testsuite.log:+/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/133/testsuite.log:./diagnostics.at:234: LC_ALL="$locale" bison -fcaret --color=debug -Wall input.y testsuite.dir/133/testsuite.log:+/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/134/testsuite.log:./diagnostics.at:257: LC_ALL="$locale" bison -fcaret --color=debug -Wall input.y testsuite.dir/134/testsuite.log:+/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/134/testsuite.log:+sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/134/testsuite.log:+sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/135/testsuite.log:./diagnostics.at:279: LC_ALL="$locale" bison -fcaret --color=debug -Wall input.y testsuite.dir/135/testsuite.log:+/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/136/testsuite.log:./diagnostics.at:307: LC_ALL="$locale" bison -fcaret --color=debug -Wall input.y testsuite.dir/136/testsuite.log:+/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/137/testsuite.log:./diagnostics.at:346: LC_ALL="$locale" COLUMNS=200 bison -fcaret --color=debug -Wall input.y testsuite.dir/137/testsuite.log:+/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/138/testsuite.log:./diagnostics.at:379: LC_ALL="$locale" COLUMNS=80 bison -fcaret --color=debug -Wall input.y testsuite.dir/138/testsuite.log:+/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/139/testsuite.log:./diagnostics.at:412: LC_ALL="$locale" COLUMNS=60 bison -fcaret --color=debug -Wall input.y testsuite.dir/139/testsuite.log:+/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) testsuite.dir/140/testsuite.log:./diagnostics.at:436: LC_ALL="$locale" bison -fcaret --color=debug -Wall input.y testsuite.dir/140/testsuite.log:+/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) Should the locale be set to POSIX to fix this? On Thu, Apr 16, 2020 at 9:50 AM Pierre Labastie <[email protected]> wrote: > On Thu, 2020-04-16 at 09:14 -0400, Bud Rozwood wrote: > > Sorry the version is Bison-3.5.2. > > > > On Thu, Apr 16, 2020 at 9:12 AM Bud Rozwood <[email protected]> > > wrote: > > > Hi, > > > > > > I've ran make check after flex was installed and I get some errors > > > regarding the diagnostic tests and I'm not sure why. I've followed > > > the book up to that point to a t. > > > > > > Although it seems that these tests are optional and even the log > > > for bison in lfs i7 test-log is empty. The test suite for flex ran > > > without errors: > > > > > > grep FAIL log_dir/chapter06/flex.txt > > > # XFAIL: 0 > > > # FAIL: 0 > > > > > > I've attached my test log for bison if you want to look at it. > > > > > > If this isn't serious, I guess I should move on. > > All the FAILED tests are in the "Diagnostics" section. Can you look at > one of the test logs (look at tests/testsuite.dir)? I suspect it has to > do with a wrong locale assumption or so, because diagnostics are all > about text... > > All in all, and if you do not want to investigate further, I'd say you > are good to go. > > Pierre > > -- > http://lists.linuxfromscratch.org/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > > Do not top post on this list. > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > http://en.wikipedia.org/wiki/Posting_style >
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
