From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Devoogdt <thomas.devoogdt@gmail.com>
Cc: Marcin Bis <marcin@bis.org.pl>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/bluez5_utils: fix build with libglib2 >= 2.69
Date: Sun, 06 Feb 2022 15:15:13 +0100 [thread overview]
Message-ID: <87pmo0w07i.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220206092357.19286-1-thomas.devoogdt@gmail.com> (Thomas Devoogdt's message of "Sun, 6 Feb 2022 10:23:57 +0100")
>>>>> "Thomas" == Thomas Devoogdt <thomas.devoogdt@gmail.com> writes:
> Fix the following build failure raised since bump of libglib2 to version
> 2.70 in commit 079923d:
> profiles/battery/battery.c:162:2: warning: 'g_memdup' is deprecated (declared at /home/buildroot/autobuild/instance-0/output-1/host/bin/../arm-buildroot-linux-gnueabi/sysroot/usr/include/glib-2.0/glib/gstrfuncs.h:257): Use 'g_memdup2' instead [-Wdeprecated-declarations]
> batt-> initial_value = g_memdup(value, length);
> Fixes:
> - http://autobuild.buildroot.org/results/6b8/6b8870d12e0804d6154230a7322c49416c1dc0e2/build-end.log
> Sources:
> - https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=710220f861b100856711a0a4d4a852874228a57a
> - https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=9f09e69ecb077082301dafb745856e1f3731aaa7
> - https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=cfab569484b18407fc117bb96634525cc76ea1f5
> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@gmail.com>
> ---
> [update] removed patch numbers & remve change to 0001-tools-mesh-cfgtest-include-limits.h
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-06 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 9:23 [Buildroot] [PATCH] package/bluez5_utils: fix build with libglib2 >= 2.69 Thomas Devoogdt
2022-02-06 14:15 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-06 9:04 Thomas Devoogdt
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=87pmo0w07i.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=marcin@bis.org.pl \
--cc=thomas.devoogdt@gmail.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.