From: Peter Xu <peterx@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org,
"Nick Briggs" <nicholas.h.briggs@gmail.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Li Zhijian" <lizhijian@fujitsu.com>,
"Kostiantyn Kostiuk" <kkostiuk@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Andrew Deason" <adeason@sinenomine.net>,
"Eric Blake" <eblake@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-arm@nongnu.org,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>
Subject: Re: [PATCH-for-10.2 2/3] migration/rdma: Check ntohll() availability with meson
Date: Mon, 17 Nov 2025 16:36:56 -0500 [thread overview]
Message-ID: <aRuVeBtzS9r3Oypr@x1.local> (raw)
In-Reply-To: <20251117203834.83713-3-philmd@linaro.org>
On Mon, Nov 17, 2025 at 09:38:33PM +0100, Philippe Mathieu-Daudé wrote:
> Commit 44ce1b5d2fc ("migration/rdma: define htonll/ntohll
> only if not predefined") tried to only include htonll/ntohll
> replacements when their symbol is *defined*, but this doesn't
> work, as they aren't:
>
> ../migration/rdma.c:242:17: error: static declaration of 'htonll' follows non-static declaration
> 242 | static uint64_t htonll(uint64_t v)
> | ^~~~~~
> In file included from /usr/include/netinet/in.h:73,
> from /usr/include/sys/socket.h:32,
> from /home/f4bug/qemu/include/system/os-posix.h:30,
> from /home/f4bug/qemu/include/qemu/osdep.h:176,
> from ../migration/rdma.c:17:
> /usr/include/sys/byteorder.h:75:18: note: previous declaration of 'htonll' with type 'uint64_t(uint64_t)' {aka 'long unsigned int(long unsigned int)'}
> 75 | extern uint64_t htonll(uint64_t);
> | ^~~~~~
> ../migration/rdma.c:252:17: error: static declaration of 'ntohll' follows non-static declaration
> 252 | static uint64_t ntohll(uint64_t v)
> | ^~~~~~
> /usr/include/sys/byteorder.h:76:18: note: previous declaration of 'ntohll' with type 'uint64_t(uint64_t)' {aka 'long unsigned int(long unsigned int)'}
> 76 | extern uint64_t ntohll(uint64_t);
> | ^~~~~~
>
> Better to check the symbol availability with meson.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Acked-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2025-11-17 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 20:38 [PATCH-for-10.2 0/3] buildsys: Fix Solaris build Philippe Mathieu-Daudé
2025-11-17 20:38 ` [PATCH-for-10.2 1/3] qga/commands: Include proper Solaris header for getloadavg() Philippe Mathieu-Daudé
2025-11-18 8:07 ` Kostiantyn Kostiuk
2025-11-18 8:50 ` Richard Henderson
2025-11-17 20:38 ` [PATCH-for-10.2 2/3] migration/rdma: Check ntohll() availability with meson Philippe Mathieu-Daudé
2025-11-17 21:36 ` Peter Xu [this message]
2025-11-18 8:48 ` Richard Henderson
2025-11-17 20:38 ` [PATCH-for-10.2 3/3] target/arm/tcg: Undefine Solaris FSCALE definition as a kludge Philippe Mathieu-Daudé
2025-11-18 8:51 ` Richard Henderson
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=aRuVeBtzS9r3Oypr@x1.local \
--to=peterx@redhat.com \
--cc=adeason@sinenomine.net \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kkostiuk@redhat.com \
--cc=lizhijian@fujitsu.com \
--cc=marcandre.lureau@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=michael.roth@amd.com \
--cc=nicholas.h.briggs@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).