From: "yezhenyu (A)" <yezhenyu2@huawei.com>
To: "Dan Horák" <dan@danny.cz>, fio@vger.kernel.org
Cc: sandeen@redhat.com, xiexiangyou@huawei.com
Subject: Re: fio fails to build on s390x and armv7 after enabling more tests
Date: Tue, 14 Jan 2020 21:29:42 +0800 [thread overview]
Message-ID: <ccf7cf6f-906a-e5f3-2bcd-c5706310cbbd@huawei.com> (raw)
In-Reply-To: <20200114111747.dbfba9c9764da37e9d26870b@danny.cz>
Hi,
Do you merge this patch?
https://git.kernel.dk/cgit/fio/commit/?id=aae515f4e1cb0b3c003e127200d344d807032a79
On 2020/1/14 18:17, Dan Horák wrote:
> Hi,
>
> our CI discovered that after
> https://git.kernel.dk/cgit/fio/commit/?id=5ad80fa7cf5be0399c8d9d68967781e56a767c82
> fio fails to build on s390x and armv7 (the builders use Fedora 31).
>
> ...
> CC t/read-to-pipe-async.o
> LINK t/read-to-pipe-async
> CC t/io_uring.o
> t/io_uring.c: In function ‘io_uring_register_buffers’:
> t/io_uring.c:103:17: error: ‘__NR_sys_io_uring_register’ undeclared (first use in this function); did you mean ‘SYS_io_uring_register’?
> 103 | return syscall(__NR_sys_io_uring_register, s->ring_fd,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> | SYS_io_uring_register
> t/io_uring.c:103:17: note: each undeclared identifier is reported only once for each function it appears in
> t/io_uring.c: In function ‘io_uring_register_files’:
> t/io_uring.c:120:17: error: ‘__NR_sys_io_uring_register’ undeclared (first use in this function); did you mean ‘SYS_io_uring_register’?
> 120 | return syscall(__NR_sys_io_uring_register, s->ring_fd,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> | SYS_io_uring_register
> t/io_uring.c: In function ‘io_uring_setup’:
> t/io_uring.c:126:17: error: ‘__NR_sys_io_uring_setup’ undeclared (first use in this function); did you mean ‘SYS_io_uring_setup’?
> 126 | return syscall(__NR_sys_io_uring_setup, entries, p);
> | ^~~~~~~~~~~~~~~~~~~~~~~
> | SYS_io_uring_setup
> t/io_uring.c: In function ‘io_uring_enter’:
> t/io_uring.c:132:17: error: ‘__NR_sys_io_uring_enter’ undeclared (first use in this function); did you mean ‘SYS_io_uring_enter’?
> 132 | return syscall(__NR_sys_io_uring_enter, s->ring_fd, to_submit,
> | ^~~~~~~~~~~~~~~~~~~~~~~
> | SYS_io_uring_enter
> t/io_uring.c: In function ‘io_uring_register_buffers’:
> t/io_uring.c:105:1: warning: control reaches end of non-void function [-Wreturn-type]
> 105 | }
> | ^
> t/io_uring.c: In function ‘io_uring_register_files’:
> t/io_uring.c:122:1: warning: control reaches end of non-void function [-Wreturn-type]
> 122 | }
> | ^
> t/io_uring.c: In function ‘io_uring_setup’:
> t/io_uring.c:127:1: warning: control reaches end of non-void function [-Wreturn-type]
> 127 | }
> | ^
> t/io_uring.c: In function ‘io_uring_enter’:
> t/io_uring.c:134:1: warning: control reaches end of non-void function [-Wreturn-type]
> 134 | }
> | ^
> make: *** [Makefile:380: t/io_uring.o] Chyba 1
>
>
> Thanks,
>
> Dan
>
> .
>
next prev parent reply other threads:[~2020-01-14 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 10:17 fio fails to build on s390x and armv7 after enabling more tests Dan Horák
2020-01-14 13:29 ` yezhenyu (A) [this message]
2020-01-14 13:55 ` Dan Horák
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=ccf7cf6f-906a-e5f3-2bcd-c5706310cbbd@huawei.com \
--to=yezhenyu2@huawei.com \
--cc=dan@danny.cz \
--cc=fio@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=xiexiangyou@huawei.com \
/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