From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Michael Nosthoff <buildroot@heine.tech>,
Marcin Bis <marcin@bis.org.pl>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/bluez5_utils: hid needs hog
Date: Wed, 28 Jul 2021 21:18:22 +0200 [thread overview]
Message-ID: <20210728211822.1d6ec57a@windsurf> (raw)
In-Reply-To: <20210727072011.2272682-1-fontaine.fabrice@gmail.com>
On Tue, 27 Jul 2021 09:20:11 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Build of hid without hog is broken since commit
> fb9fc969d91f69851b4c70dba512b607e52bda7b:
>
> /home/buildroot/autobuild/instance-3/output-1/host/opt/ext-toolchain/bin/../lib/gcc/i586-buildroot-linux-musl/9.3.0/../../../../i586-buildroot-linux-musl/bin/ld: profiles/input/bluetoothd-manager.o: in function `input_init':
> manager.c:(.text+0x2fd): undefined reference to `input_set_auto_sec'
>
> Fixes:
> - http://autobuild.buildroot.org/results/9222879c9fe958e01e33f69531270355ea016d17
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/bluez5_utils/Config.in | 1 +
> 1 file changed, 1 insertion(+)
I have applied, but as I said earlier, I think this should be fixed
upstream, and depending on the upstream fix, perhaps this needs to be
reverted in Buildroot, or changed.
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-28 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 7:20 [Buildroot] [PATCH 1/1] package/bluez5_utils: hid needs hog Fabrice Fontaine
2021-07-27 7:43 ` Thomas Petazzoni
2021-07-27 7:57 ` Michael Nosthoff via buildroot
2021-07-28 19:18 ` 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=20210728211822.1d6ec57a@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=buildroot@heine.tech \
--cc=fontaine.fabrice@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox