From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fiona Klute via buildroot <buildroot@buildroot.org>
Cc: Fiona Klute <fiona.klute@gmx.de>,
Grzegorz Blach <grzegorz@blach.pl>,
Marcin Bis <marcin@bis.org.pl>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 1/4] package/bluez5_utils{, -headers}: bump version to 5.79
Date: Tue, 31 Dec 2024 11:54:47 +0100 [thread overview]
Message-ID: <20241231115447.32f36592@windsurf> (raw)
In-Reply-To: <20241210162243.1541113-1-fiona.klute@gmx.de>
Hello Fiona,
On Tue, 10 Dec 2024 17:22:39 +0100
Fiona Klute via buildroot <buildroot@buildroot.org> wrote:
> From: "Fiona Klute (WIWA)" <fiona.klute@gmx.de>
>
> Upstream changelog:
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.79&id=0845b8f6ef2ac004b1c953cf4fe4ca3458cd8e36
>
> Patch for musl compatibility taken from upstream "master".
>
> Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
> ---
> .../bluez5_utils-headers.mk | 2 +-
> ...0001-gdbus-define-MAX_INPUT-for-musl.patch | 33 +++++++++++++++++++
> package/bluez5_utils/bluez5_utils.hash | 2 +-
> package/bluez5_utils/bluez5_utils.mk | 2 +-
> 4 files changed, 36 insertions(+), 3 deletions(-)
> create mode 100644 package/bluez5_utils/0001-gdbus-define-MAX_INPUT-for-musl.patch
It looks like this update is causing a few build failures:
http://autobuild.buildroot.net/?reason=bluez5_utils-5.79
Like this:
/home/autobuild/autobuild/instance-7/output-1/host/lib/gcc/mips-buildroot-linux-musl/13.3.0/../../../../mips-buildroot-linux-musl/bin/ld: profiles/input/bluetoothd-hog.o: in function `hog_disconnect':
/home/autobuild/autobuild/instance-7/output-1/build/bluez5_utils-5.79/profiles/input/hog.c:211:(.text.hog_disconnect+0x3c): undefined reference to `input_get_userspace_hid'
/home/autobuild/autobuild/instance-7/output-1/host/lib/gcc/mips-buildroot-linux-musl/13.3.0/../../../../mips-buildroot-linux-musl/bin/ld: /home/autobuild/autobuild/instance-7/output-1/build/bluez5_utils-5.79/profiles/input/hog.c:211:(.text.hog_disconnect+0x44): undefined reference to `input_get_userspace_hid'
collect2: error: ld returned 1 exit status
Could you have a look perhaps?
Thanks a lot!
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:[~2024-12-31 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 16:22 [Buildroot] [PATCH v2 1/4] package/bluez5_utils{, -headers}: bump version to 5.79 Fiona Klute via buildroot
2024-12-10 16:22 ` [Buildroot] [PATCH v2 2/4] package/bluez5_utils: fix dbusconfdir Fiona Klute via buildroot
2024-12-10 16:22 ` [Buildroot] [PATCH v2 3/4] package/bluez5_utils: install datafiles with correct permissions Fiona Klute via buildroot
2024-12-10 16:22 ` [Buildroot] [PATCH v2 4/4] package/bluez5_utils: tidy up the init script Fiona Klute via buildroot
2024-12-29 22:35 ` [Buildroot] [PATCH v2 1/4] package/bluez5_utils{, -headers}: bump version to 5.79 Thomas Petazzoni via buildroot
2024-12-31 10:54 ` Thomas Petazzoni [this message]
2024-12-31 14:59 ` Fiona Klute via buildroot
2024-12-31 15:59 ` Thomas Petazzoni 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=20241231115447.32f36592@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=fontaine.fabrice@gmail.com \
--cc=grzegorz@blach.pl \
--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.