From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Hal Rosenstock <hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
RDMA mailing list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: librdmacm in rdma-core build warnings
Date: Mon, 2 Oct 2017 11:54:31 -0600 [thread overview]
Message-ID: <20171002175431.GB13149@obsidianresearch.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A82373AB199DAC-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Mon, Oct 02, 2017 at 04:11:01PM +0000, Hefty, Sean wrote:
> > [26/189] Building C object
> > librdmacm/CMakeFiles/rspreload.dir/preload.c.o
> > ../librdmacm/preload.c:818:9: warning: no previous prototype for
> > ???readv??? [-Wmissing-prototypes] ssize_t readv(int socket, const struct
> > iovec *iov, int iovcnt)
> > ^~~~~
> > ../librdmacm/preload.c:857:9: warning: no previous prototype for
> > ???writev??? [-Wmissing-prototypes] ssize_t writev(int socket, const
> > struct iovec *iov, int iovcnt)
>
> Does including sys/uio.h fix this?
Something like that is the right solution, probably caused by glibc
changes not gcc changes...
The prototype must come from glibc headers.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-10-02 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 6:15 librdmacm in rdma-core build warnings Leon Romanovsky
[not found] ` <20171002061532.GJ2031-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-10-02 16:11 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373AB199DAC-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2017-10-02 17:54 ` Jason Gunthorpe [this message]
[not found] ` <20171002175431.GB13149-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-10-02 18:27 ` Leon Romanovsky
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=20171002175431.GB13149@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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