diff options
Diffstat (limited to 'results/classifier/108/other/1886343')
| -rw-r--r-- | results/classifier/108/other/1886343 | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/results/classifier/108/other/1886343 b/results/classifier/108/other/1886343 new file mode 100644 index 000000000..0c360a6c9 --- /dev/null +++ b/results/classifier/108/other/1886343 @@ -0,0 +1,36 @@ +graphic: 0.799 +device: 0.746 +semantic: 0.746 +other: 0.677 +performance: 0.667 +files: 0.612 +network: 0.576 +permissions: 0.548 +vnc: 0.504 +boot: 0.485 +debug: 0.453 +socket: 0.434 +PID: 0.433 +KVM: 0.299 + +configure has non-posix bash syntax + +which gives an error when run on a system that uses dash for /bin/sh. + +The problem is at line 6464 which has + if test "$have_keyring" == "yes" +the double equal sign is non-posix bash syntax that isn't accepted by posix shells like dash. This was added 2020-05-25 according to git blame so looks like a recent problem. + +On an Ubuntu 20.04 system with top of tree sources I get +gondor:2027$ ../qemu/configure --prefix=/home/wilson/FOSS/qemu/install-qemu-tmp --target-list=riscv64-linux-user,riscv64-softmmu,riscv32-linux-user,riscv32-softmmu +../qemu/configure: 6464: test: yes: unexpected operator +... + +configure completes OK, so this is a minor problem. It is just one configure test that is failing to work properly. + +Thanks for reporting! Seems like others ran into this problem, too - a patch is already on the list: +https://lists.gnu.org/archive/html/qemu-devel/2020-06/msg08967.html + +Fixed in commit b418d2656112174c; this will be in QEMU 5.1. + + |