From: Fam Zheng <fam@euphon.net>
To: Laurent Vivier <laurent@vivier.eu>
Cc: "patchew-devel@redhat.com" <patchew-devel@redhat.com>,
aleksandar.markovic@rt-rk.com, qemu-devel@nongnu.org,
amarkovic@wavecomp.com
Subject: Re: [Qemu-devel] [Patchew-devel] [PATCH v15 0/5] linux-user: A set of miscellaneous patches
Date: Fri, 28 Jun 2019 20:41:17 +0800 [thread overview]
Message-ID: <20190628124117.2lltlf7yiwlwy4j4@debian> (raw)
In-Reply-To: <f1ff093c-cb64-a54e-778e-eb18a0fdddb2@vivier.eu>
On Fri, 06/28 14:15, Laurent Vivier wrote:
> Dear Patchew developers,
>
> Le 28/06/2019 à 11:49, no-reply@patchew.org a écrit :
> > Patchew URL: https://patchew.org/QEMU/1561712082-31441-1-git-send-email-aleksandar.markovic@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-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/patchew-devel
next prev parent reply other threads:[~2019-06-28 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 8:54 [Qemu-devel] [PATCH v15 0/5] linux-user: A set of miscellaneous patches Aleksandar Markovic
2019-06-28 8:54 ` [Qemu-devel] [PATCH v15 1/5] linux-user: Add support for translation of statx() syscall Aleksandar Markovic
2019-06-28 8:54 ` [Qemu-devel] [PATCH v15 2/5] linux-user: Add support for strace for " Aleksandar Markovic
2019-06-28 8:54 ` [Qemu-devel] [PATCH v15 3/5] linux-user: Fix target_flock structure for MIPS O64 ABI Aleksandar Markovic
2019-06-28 8:54 ` [Qemu-devel] [PATCH v15 4/5] linux-user: Introduce TARGET_HAVE_ARCH_STRUCT_FLOCK Aleksandar Markovic
2019-06-28 8:54 ` [Qemu-devel] [PATCH v15 5/5] linux-user: Handle EXCP_FPE properly for MIPS Aleksandar Markovic
2019-06-28 9:06 ` Laurent Vivier
2019-06-28 9:09 ` [Qemu-devel] [PATCH v15 0/5] linux-user: A set of miscellaneous patches no-reply
2019-06-28 9:39 ` no-reply
2019-06-28 9:49 ` no-reply
2019-06-28 12:15 ` Laurent Vivier
2019-06-28 12:41 ` Fam Zheng [this message]
2019-06-28 12:47 ` [Qemu-devel] [Patchew-devel] " Laurent Vivier
2019-06-28 12:55 ` Aleksandar Markovic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190628124117.2lltlf7yiwlwy4j4@debian \
--to=fam@euphon.net \
--cc=aleksandar.markovic@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=laurent@vivier.eu \
--cc=patchew-devel@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).