1 files changed, 42 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/857 b/results/classifier/118/graphic/857
new file mode 100644
index 000000000..436f01d84
--- /dev/null
+++ b/results/classifier/118/graphic/857
@@ -0,0 +1,42 @@
+x86: 0.989
+architecture: 0.967
+graphic: 0.931
+device: 0.872
+files: 0.856
+semantic: 0.828
+debug: 0.803
+network: 0.735
+performance: 0.706
+mistranslation: 0.675
+socket: 0.669
+PID: 0.652
+register: 0.599
+permissions: 0.599
+vnc: 0.562
+peripherals: 0.508
+user-level: 0.490
+ppc: 0.465
+arm: 0.411
+risc-v: 0.361
+boot: 0.350
+TCG: 0.307
+VMM: 0.290
+kernel: 0.226
+virtual: 0.170
+i386: 0.133
+hypervisor: 0.120
+assembly: 0.106
+KVM: 0.084
+
+qemu-x86_64 uses host libraries instead of emulated system libraries
+Description of problem:
+I'm using Buildroot to build a cross-compiled embedded Linux system. During the build process there is a little hack to create some header file using a cross-compiled application. For this hack they use qemu to run this application. Building this embedded system for aarch64 work fine, but for x86_64 I get the following messages:
+
+bytecode_builtins_list_generator: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by bytecode_builtins_list_generator)
+bytecode_builtins_list_generator: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by bytecode_builtins_list_generator)
+bytecode_builtins_list_generator: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by bytecode_builtins_list_generator)
+bytecode_builtins_list_generator: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by bytecode_builtins_list_generator)
+
+The path of the libraries in this error message is from my host system. The embedded system uses /lib64 or /usr/lib64. It seems to me that the linker search for the libraries at first on the host system and later uses the path from the command line. So you have a mixed up of host and embedded system libraries (as you can see in the attached strace log).
+Additional information:
+[qemu-1.log](/uploads/f53e98b6b15cce7cbf94d14dffa39f90/qemu-1.log)