On Fri, 06/28 14:15, Laurent Vivier wrote: > Dear Patchew developers, > > Le 28/06/2019 à 11:49, no-re...@patchew.org a écrit : > > Patchew URL: > > https://patchew.org/QEMU/1561712082-31441-1-git-send-email-aleksandar.marko...@rt-rk.com/ > > > > > > > > Hi, > > > > This series failed build test on s390x host. Please find the details below. > > To debug this kind of problem (at least to reproduce it), it may be > interesting to know the OS release of the target build environment > (glibc version, gcc version, ...) on which the build fails. > > Is this possible to add this in the mail (or in the logs)?
I've moved the env/rpm/uname commands before the actual testing commands, so the information can be collected even upon failures. Fam > > ... > > CC microblaze-linux-user/linux-user/strace.o > > CC mips64el-linux-user/linux-user/syscall.o > > LINK microblazeel-linux-user/qemu-microblazeel > > /var/tmp/patchew-tester-tmp-tr0wvoyz/src/linux-user/syscall.c:322:16: > > error: conflicting types for ‘statx’ > > 322 | _syscall5(int, statx, int, dirfd, const char *, pathname, int, > > flags, > > | ^~~~~ > > /var/tmp/patchew-tester-tmp-tr0wvoyz/src/linux-user/syscall.c:213:13: note: > > in definition of macro ‘_syscall5’ > > Thanks, > Laurent > > _______________________________________________ > Patchew-devel mailing list > patchew-de...@redhat.com > https://www.redhat.com/mailman/listinfo/patchew-devel
