From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Florian Larysch <fl@n621.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/start-stop-daemon: fix build issues with musl and GCC 14
Date: Sat, 16 Aug 2025 22:30:57 +0200 [thread overview]
Message-ID: <20250816223057.689bd7f2@windsurf> (raw)
In-Reply-To: <20250813201355.6232-1-fl@n621.de>
On Wed, 13 Aug 2025 22:13:54 +0200
Florian Larysch <fl@n621.de> wrote:
> Unlike glibc and uClibc, musl doesn't play tricks with transparent
> unions for the second argument to bind() to accept the various sockaddr
> variants, but rather just defines it as "struct sockaddr*". As GCC 14 no
> longer allows arbitrary implicit pointer casts, this results in a build
> error. Import the upstream patch that adds the cast.
>
> Fixes: https://autobuild.buildroot.org/results/00b/00b42a35a80c2deb61f2cd40aedd231597bbb290
> Signed-off-by: Florian Larysch <fl@n621.de>
> ---
> ...t-sockaddr_un-to-struct-sockaddr-on-.patch | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
> create mode 100644 package/start-stop-daemon/0003-s-s-d-Cast-struct-sockaddr_un-to-struct-sockaddr-on-.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-16 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 20:13 [Buildroot] [PATCH 1/1] package/start-stop-daemon: fix build issues with musl and GCC 14 Florian Larysch
2025-08-16 20:30 ` Thomas Petazzoni via buildroot [this message]
2025-08-21 19:21 ` Thomas Perale via buildroot
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=20250816223057.689bd7f2@windsurf \
--to=buildroot@buildroot.org \
--cc=fl@n621.de \
--cc=thomas.petazzoni@bootlin.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 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.