qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: no-reply@patchew.org
To: aleksandar.markovic@rt-rk.com
Cc: qemu-devel@nongnu.org, amarkovic@wavecomp.com, laurent@vivier.eu
Subject: Re: [Qemu-devel] [PATCH v15 0/5] linux-user: A set of miscellaneous patches
Date: Fri, 28 Jun 2019 02:49:55 -0700 (PDT)	[thread overview]
Message-ID: <156171539473.6332.3788894025347542150@c4a48874b076> (raw)
In-Reply-To: <1561712082-31441-1-git-send-email-aleksandar.markovic@rt-rk.com>

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.

=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
# HEAD pointing to a commit that has the patches applied on top of "base"
# branch
set -e
CC=$HOME/bin/cc
INSTALL=$PWD/install
BUILD=$PWD/build
mkdir -p $BUILD $INSTALL
SRC=$PWD
cd $BUILD
$SRC/configure --cc=$CC --prefix=$INSTALL
make -j4
# XXX: we need reliable clean up
# make check -j4 V=1
make install

echo
echo "=== ENV ==="
env

echo
echo "=== PACKAGES ==="
rpm -qa
=== TEST SCRIPT END ===

  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’


The full log is available at
http://patchew.org/logs/1561712082-31441-1-git-send-email-aleksandar.markovic@rt-rk.com/testing.s390x/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com

  parent reply	other threads:[~2019-06-28  9:51 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 [this message]
2019-06-28 12:15   ` Laurent Vivier
2019-06-28 12:41     ` [Qemu-devel] [Patchew-devel] " Fam Zheng
2019-06-28 12:47       ` 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=156171539473.6332.3788894025347542150@c4a48874b076 \
    --to=no-reply@patchew.org \
    --cc=aleksandar.markovic@rt-rk.com \
    --cc=amarkovic@wavecomp.com \
    --cc=laurent@vivier.eu \
    --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).