Message ID | 20220108075930.213063-1-bernd.kuhls@t-online.de |
---|---|
State | Accepted |
Headers | show |
Series | [1/1] package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.63 | expand |
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes: > Release notes: http://www.bluez.org/release-of-bluez-5-63/ The release notes mentions new build options for sanitizers, and it looks to be enabled by default: checking whether /home/peko/source/buildroot/output-bluez/host/bin/aarch64-linux-gnu-gcc accepts -fPIE... yes checking whether /home/peko/source/buildroot/output-bluez/host/bin/aarch64-linux-gnu-gcc accepts -fsanitize=address... yes checking whether /home/peko/source/buildroot/output-bluez/host/bin/aarch64-linux-gnu-gcc accepts -fsanitize=leak... yes checking whether /home/peko/source/buildroot/output-bluez/host/bin/aarch64-linux-gnu-gcc accepts -fsanitize=undefined... yes So I've added explicit --disable-* options for those. I also see that we are not explicitly disabling the -fpie logic (where we want the Buildroot option to decide if it should be used or not), so I've also added --disable-pie. Committed with these fixes, thanks.
diff --git a/package/bluez5_utils-headers/bluez5_utils-headers.mk b/package/bluez5_utils-headers/bluez5_utils-headers.mk index e671431093..5bfc652355 100644 --- a/package/bluez5_utils-headers/bluez5_utils-headers.mk +++ b/package/bluez5_utils-headers/bluez5_utils-headers.mk @@ -5,7 +5,7 @@ ################################################################################ # Keep the version and patches in sync with bluez5_utils -BLUEZ5_UTILS_HEADERS_VERSION = 5.62 +BLUEZ5_UTILS_HEADERS_VERSION = 5.63 BLUEZ5_UTILS_HEADERS_SOURCE = bluez-$(BLUEZ5_UTILS_VERSION).tar.xz BLUEZ5_UTILS_HEADERS_SITE = $(BR2_KERNEL_MIRROR)/linux/bluetooth BLUEZ5_UTILS_HEADERS_DL_SUBDIR = bluez5_utils diff --git a/package/bluez5_utils/bluez5_utils.hash b/package/bluez5_utils/bluez5_utils.hash index 3ec4acac7f..a8f5399fa6 100644 --- a/package/bluez5_utils/bluez5_utils.hash +++ b/package/bluez5_utils/bluez5_utils.hash @@ -1,5 +1,5 @@ # From https://www.kernel.org/pub/linux/bluetooth/sha256sums.asc: -sha256 38090a5b750e17fc08d3e52178ed8d3254c5f4bd2c48830d5c1955b88e3bc0c2 bluez-5.62.tar.xz +sha256 9349e11e8160bb3d720835d271250d8a7424d3690f5289e6db6fe07cc66c6d76 bluez-5.63.tar.xz # Locally computed sha256 b499eddebda05a8859e32b820a64577d91f1de2b52efa2a1575a2cb4000bc259 COPYING sha256 ec60b993835e2c6b79e6d9226345f4e614e686eb57dc13b6420c15a33a8996e5 COPYING.LIB diff --git a/package/bluez5_utils/bluez5_utils.mk b/package/bluez5_utils/bluez5_utils.mk index cf46d6e0d6..8cb9e42d72 100644 --- a/package/bluez5_utils/bluez5_utils.mk +++ b/package/bluez5_utils/bluez5_utils.mk @@ -5,7 +5,7 @@ ################################################################################ # Keep the version and patches in sync with bluez5_utils-headers -BLUEZ5_UTILS_VERSION = 5.62 +BLUEZ5_UTILS_VERSION = 5.63 BLUEZ5_UTILS_SOURCE = bluez-$(BLUEZ5_UTILS_VERSION).tar.xz BLUEZ5_UTILS_SITE = $(BR2_KERNEL_MIRROR)/linux/bluetooth BLUEZ5_UTILS_INSTALL_STAGING = YES
Release notes: http://www.bluez.org/release-of-bluez-5-63/ Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> --- package/bluez5_utils-headers/bluez5_utils-headers.mk | 2 +- package/bluez5_utils/bluez5_utils.hash | 2 +- package/bluez5_utils/bluez5_utils.mk | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)