From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <hongxu.jia@windriver.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/2] socat: 1.8.0.3 -> 1.8.1.0
Date: Tue, 16 Dec 2025 10:40:03 +0100 [thread overview]
Message-ID: <DEZJIBHT7GKY.AIXJ4FBZHXER@bootlin.com> (raw)
In-Reply-To: <20251215084345.1797393-2-hongxu.jia@windriver.com>
On Mon Dec 15, 2025 at 9:43 AM CET, hongxu via lists.openembedded.org wrote:
> License-Update: No change, update README to add new lines
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
Hi Hongxu,
Thanks for your patch.
It looks like the new version is having build issues with musl:
ERROR: socat-1.8.1.0-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86-64-v3-poky-linux-musl/socat/1.8.1.0/temp/run.do_compile.476916' failed with exit code 1
...
| ../sources/socat-1.8.1.0/xio-netlink.c: In function 'xio_netlink_mtu':
| ../sources/socat-1.8.1.0/xio-netlink.c:33:59: error: initialization of 'int' from 'void *' makes integer from pointer without a cast [-Wint-conversion]
| 33 | struct msghdr rtmsg = { &sa, sizeof(sa), &iov, 1, NULL, 0, 0 };
| | ^~~~
| ../sources/socat-1.8.1.0/xio-netlink.c:33:59: note: (near initialization for 'rtmsg.__pad1')
| make: *** [<builtin>: xio-netlink.o] Error 1
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-12-16 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 8:43 [PATCH 1/2] libgpg-error: 1.56 -> 1.58 Hongxu Jia
2025-12-15 8:43 ` [PATCH 2/2] socat: 1.8.0.3 -> 1.8.1.0 Hongxu Jia
2025-12-16 9:40 ` Mathieu Dubois-Briand [this message]
2025-12-16 9:41 ` [OE-core] " Mathieu Dubois-Briand
2025-12-16 9:53 ` Hongxu Jia
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=DEZJIBHT7GKY.AIXJ4FBZHXER@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.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.