From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Michael Nosthoff via buildroot <buildroot@busybox.net>
Cc: Michael Nosthoff <buildroot@heine.tech>,
Marcin Bis <marcin@bis.org.pl>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/bluez5_utils: fix mesh build with musl
Date: Sat, 24 Jul 2021 09:53:26 +0200 [thread overview]
Message-ID: <20210724095326.19eb1fc5@windsurf> (raw)
In-Reply-To: <20210723132648.30775-1-buildroot@heine.tech>
On Fri, 23 Jul 2021 15:26:46 +0200
Michael Nosthoff via buildroot <buildroot@busybox.net> wrote:
> when compiling with mesh support and musl toolchain the build fails
> due to a missing include of limits.h for PATH_MAX in mesh-cfgtest.c.
>
> Patch submitted upstream:
> https://lore.kernel.org/linux-bluetooth/20210723081039.30396-1-bluez@heine.tech
>
> Fixes:
> http://autobuild.buildroot.net/results/20cc47f54de0b0d4bdf108c3715c590ae8ab476f/
> http://autobuild.buildroot.net/results/003968b25906579dbcf5a95d1e43fec0ab504ef5/
>
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
> ---
> ...-tools-mesh-cfgtest-include-limits.h.patch | 32 +++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 package/bluez5_utils/0001-tools-mesh-cfgtest-include-limits.h.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-07-24 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 13:26 [Buildroot] [PATCH v2] package/bluez5_utils: fix mesh build with musl Michael Nosthoff via buildroot
2021-07-23 13:34 ` Michael Nosthoff via buildroot
2021-07-24 7:53 ` Thomas Petazzoni [this message]
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=20210724095326.19eb1fc5@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=buildroot@heine.tech \
--cc=marcin@bis.org.pl \
/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.