1 files changed, 66 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1568589 b/results/classifier/zero-shot/108/other/1568589
new file mode 100644
index 000000000..28acdf252
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/1568589
@@ -0,0 +1,66 @@
+device: 0.917
+graphic: 0.909
+semantic: 0.851
+files: 0.827
+PID: 0.813
+other: 0.798
+debug: 0.711
+permissions: 0.681
+socket: 0.663
+network: 0.646
+performance: 0.633
+vnc: 0.585
+boot: 0.526
+KVM: 0.093
+
+Compile for os x host failed
+
+Hello QEMU,
+
+I try compile qemu from git pulled by me today and have a troubles:
+
+ GEN   trace/generated-helpers.c
+  CC    aarch64-softmmu/trace/generated-helpers.o
+  LINK  aarch64-softmmu/qemu-system-aarch64
+Undefined symbols for architecture x86_64:
+  "_event_notifier_init_fd", referenced from:
+      _process_msg in ivshmem.o
+ld: symbol(s) not found for architecture x86_64
+clang: error: linker command failed with exit code 1 (use -v to see invocation)
+make[1]: *** [qemu-system-aarch64] Error 1
+make: *** [subdir-aarch64-softmmu] Error 2
+
+Host: 
+# uname -a
+Darwin MacBook-Pro 15.4.0 Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64
+
+# ./configure
+Configure: http://pastebin.com/L9ytLFDE
+
+# make -v
+GNU Make 3.81
+Copyright (C) 2006  Free Software Foundation, Inc.
+This is free software; see the source for copying conditions.
+There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
+PARTICULAR PURPOSE.
+
+This program built for i386-apple-darwin11.3.0
+
+Also for i386
+
+  LINK  i386-softmmu/qemu-system-i386
+Undefined symbols for architecture x86_64:
+  "_event_notifier_init_fd", referenced from:
+      _process_msg in ivshmem.o
+ld: symbol(s) not found for architecture x86_64
+clang: error: linker command failed with exit code 1 (use -v to see invocation)
+make[1]: *** [qemu-system-i386] Error 1
+make: *** [subdir-i386-softmmu] Error 2
+
+fix: http://patchwork.ozlabs.org/patch/603499/
+
+According to the discussion for the patch that you've mentioned, the problem should go away after a "make distclean". Can you still reproduce it after doing a fresh build?
+
+Closing this bug since the submitter never responded to Thomas' query in comment #4 in 2016, and we believe it to have been a transient issue fixed by 'make distclean'.
+
+