[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: riscv32, qemu-user: semi-functional, what goes wrong?
From: |
Andreas K. Huettel |
Subject: |
Re: riscv32, qemu-user: semi-functional, what goes wrong? |
Date: |
Tue, 12 Sep 2023 22:46:13 +0200 |
Am Dienstag, 12. September 2023, 21:55:13 CEST schrieb Chet Ramey:
>
> > run-posixexp
> > 309d308
> > < ./posixexp.tests: line 98: syntax error: unexpected end of file
>
> Did you remake y.tab.c? And if so, what version of bison did you use?
Not deliberately, but this is 5.2_p15, so if one of the patches touches the
source...
riscv32 ~ # bison --version
bison (GNU Bison) 3.8.2
I just re-ran the bash build, and the log contains a line
bison -y -d ./parse.y
Full xz'ed build log is 11kbyte.
>
> > run-read
> > warning: please do not consider output differing only in the amount of
> > warning: white space to be an error.
> > 47c47
> > < a
> > ---
> >> abcde
> > 71c71
> > < 0
> > ---
> >> 1
> > 74c74
> > < 1
> > ---
> >> timeout 2: ok
> > 80c80
> > < a
> > ---
> >> abcde
>
> These indicate that read with a timeout through a pipe or from /dev/tty is
> failing (or very slow) for some reason. It's strange, since the data is
> already written to the pipe and waiting to be read when the `read' builtin
> is called. The /dev/tty tests can be fooled by typeahead while the tests
> are running, but that doesn't usually happen.
Could a timeout also mean that part of the data "got lost" and it's
trying to read more than is available?
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
signature.asc
Description: This is a digitally signed message part.