All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: How does CI system get updated?
Date: Thu, 25 Jul 2024 07:55:06 -0700	[thread overview]
Message-ID: <20240725075506.207aad84@hermes.local> (raw)



This warning is due to a very old version of Mingw installed in CI system.

==== 20 line log output for Windows Server 2019 (dpdk_mingw64_compile): ====
In file included from ..\lib\net/rte_ip.h:21,
from ../lib/net/rte_dissect.c:20:
C:/mingw64/mingw64/x86_64-w64-mingw32/include/ws2tcpip.h:447:63: note: expected 'PVOID' {aka 'void *'} but argument is of type 'const uint8_t *' {aka 'const unsigned char *'}
WINSOCK_API_LINKAGE LPCSTR WSAAPI InetNtopA(INT Family, PVOID pAddr, LPSTR pStringBuf, size_t StringBufSize);
~~~~~~^~~~~
../lib/net/rte_dissect.c:292:29: error: passing argument 2 of 'inet_ntop' discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]
inet_ntop(AF_INET6, ip6_hdr->dst_addr, dbuf, sizeof(dbuf));
~~~~~~~^~~~~~~~~~
In file included from ..\lib\net/rte_ip.h:21,
from ../lib/net/rte_dissect.c:20:
C:/mingw64/mingw64/x86_64-w64-mingw32/include/ws2tcpip.h:447:63: note: expected 'PVOID' {aka 'void *'} but argument is of type 'const uint8_t *' {aka 'const unsigned char *'}
WINSOCK_API_LINKAGE LPCSTR WSAAPI InetNtopA(INT Family, PVOID pAddr, LPSTR pStringBuf, size_t StringBufSize);
~~~~~~^~~~~

It was fixed upstream in Mingw 4 years ago.

             reply	other threads:[~2024-07-25 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 14:55 Stephen Hemminger [this message]
2024-07-25 19:06 ` How does CI system get updated? Patrick Robb
2024-07-26 16:34   ` Patrick Robb
2024-07-26 17:27     ` Stephen Hemminger

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=20240725075506.207aad84@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.