From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Marcin Bis <marcin@bis.org.pl>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/bluez5_utils: fix sixaxis build without tools
Date: Thu, 9 May 2024 16:08:04 +0200 [thread overview]
Message-ID: <20240509160804.68729fc6@windsurf> (raw)
In-Reply-To: <20240509074932.4786-1-fontaine.fabrice@gmail.com>
On Thu, 9 May 2024 09:49:32 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following build failure raised since bump to version 5.75 in
> commit b890206876588ed0d16187abf49d35a45177cc3d and
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=9f71892b63f6b65dab874a633d88ae2dcad93a16:
>
> /home/autobuild/autobuild/instance-2/output-1/host/lib/gcc/x86_64-buildroot-linux-musl/12.3.0/../../../../x86_64-buildroot-linux-musl/bin/ld: plugins/bluetoothd-sixaxis.o: in function `sixaxis_init':
> sixaxis.c:(.text.sixaxis_init+0x23): undefined reference to `udev_new'
>
> Fixes: b890206876588ed0d16187abf49d35a45177cc3d
> - http://autobuild.buildroot.org/results/c337d0f473c5fbb3e6cda1317ba06f5e2b16a43e
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...e.ac-fix-sixaxis-build-without-tools.patch | 35 +++++++++++++++++++
> package/bluez5_utils/bluez5_utils.mk | 1 +
> 2 files changed, 36 insertions(+)
> create mode 100644 package/bluez5_utils/0002-configure.ac-fix-sixaxis-build-without-tools.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
prev parent reply other threads:[~2024-05-09 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 7:49 [Buildroot] [PATCH 1/1] package/bluez5_utils: fix sixaxis build without tools Fabrice Fontaine
2024-05-09 14:08 ` Thomas Petazzoni via buildroot [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=20240509160804.68729fc6@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=marcin@bis.org.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox