summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/other/1793183
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/108/other/1793183')
-rw-r--r--results/classifier/zero-shot/108/other/179318384
1 files changed, 84 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1793183 b/results/classifier/zero-shot/108/other/1793183
new file mode 100644
index 000000000..8624f913c
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/1793183
@@ -0,0 +1,84 @@
+permissions: 0.776
+graphic: 0.770
+performance: 0.712
+device: 0.697
+debug: 0.694
+semantic: 0.657
+other: 0.645
+socket: 0.633
+PID: 0.623
+files: 0.606
+boot: 0.603
+KVM: 0.575
+network: 0.561
+vnc: 0.470
+
+apt source --compile qemu-system-x86 fails on last ubuntu 18.04.1
+
+Error log:
+
+/tmp/qemu-2.10+dfsg/util/memfd.c:40:12: error: static declaration of ‘memfd_create’ follows non-static declaration
+ static int memfd_create(const char *name, unsigned int flags)
+            ^~~~~~~~~~~~
+In file included from /usr/include/x86_64-linux-gnu/bits/mman-linux.h:115:0,
+                 from /usr/include/x86_64-linux-gnu/bits/mman.h:45,
+                 from /usr/include/x86_64-linux-gnu/sys/mman.h:41,
+                 from /tmp/qemu-2.10+dfsg/include/sysemu/os-posix.h:29,
+                 from /tmp/qemu-2.10+dfsg/include/qemu/osdep.h:104,
+                 from /tmp/qemu-2.10+dfsg/util/memfd.c:28:
+/usr/include/x86_64-linux-gnu/bits/mman-shared.h:46:5: note: previous declaration of ‘memfd_create’ was here
+ int memfd_create (const char *__name, unsigned int __flags) __THROW;
+     ^~~~~~~~~~~~
+/tmp/qemu-2.10+dfsg/rules.mak:66: recipe for target 'util/memfd.o' failed
+make[1]: *** [util/memfd.o] Error 1
+make[1]: *** Waiting for unfinished jobs....
+make[1]: Leaving directory '/tmp/qemu-2.10+dfsg/qemu-build'
+debian/rules:121: recipe for target 'build-stamp' failed
+make: *** [build-stamp] Error 2
+dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
+
+
+
+The attachment "fix-memfd-conflict.patch" seems to be a patch.  If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
+
+[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]
+
+On 18 September 2018 at 10:24, Dmitry Isaykin <email address hidden> wrote:
+> Public bug reported:
+>
+> Error log:
+>
+> /tmp/qemu-2.10+dfsg/util/memfd.c:40:12: error: static declaration of ‘memfd_create’ follows non-static declaration
+>  static int memfd_create(const char *name, unsigned int flags)
+>             ^~~~~~~~~~~~
+> In file included from /usr/include/x86_64-linux-gnu/bits/mman-linux.h:115:0,
+>                  from /usr/include/x86_64-linux-gnu/bits/mman.h:45,
+>                  from /usr/include/x86_64-linux-gnu/sys/mman.h:41,
+>                  from /tmp/qemu-2.10+dfsg/include/sysemu/os-posix.h:29,
+>                  from /tmp/qemu-2.10+dfsg/include/qemu/osdep.h:104,
+>                  from /tmp/qemu-2.10+dfsg/util/memfd.c:28:
+> /usr/include/x86_64-linux-gnu/bits/mman-shared.h:46:5: note: previous declaration of ‘memfd_create’ was here
+>  int memfd_create (const char *__name, unsigned int __flags) __THROW;
+>      ^~~~~~~~~~~~
+> /tmp/qemu-2.10+dfsg/rules.mak:66: recipe for target 'util/memfd.o' failed
+
+This is fixed in upstream QEMU in commit 75e5b70e6b5dcc, which is in
+QEMU 2.12.0. If Ubuntu are interested in fixing this they can backport
+that to the QEMU they are shipping, or alternatively move forward to 2.12.
+
+thanks
+-- PMM
+
+
+This was already fixed in bionic's 1:2.11+dfsg-1ubuntu4, and the current version of the package in bionic is 1:2.11+dfsg-1ubuntu7.5.
+
+I just tried a build in bionic and it finished just fine.
+
+Looking at the tmp directory of your build, you seem to be using an older version:
+/tmp/qemu-2.10+dfsg/util/memfd.c:40:12: error: static......
+
+I will therefore mark this bug as invalid. If you believe that to be a mistake, please reopen it with further information.
+
+Thanks!
+
+