It builds and completes the tests with gcc7 built from the AUR and the following changes, some of the other changes from gripped to remove unused bits could be added:
$ diff -u origPKGBUILD PKGBUILD
--- origPKGBUILD 2019-06-08 15:08:09.232347589 +0100
+++ PKGBUILD 2019-06-08 15:04:51.642326443 +0100
@@ -30,6 +30,7 @@
build() {
cd ${srcdir}/${_gitname}
+ export CC=/usr/bin/gcc-7
./configure \
--prefix=/usr \
--mandir=/usr/share/man \
@@ -37,6 +38,7 @@
--localstatedir=/var \
--libexecdir=/usr/lib \
--enable-sixaxis \
+ --enable-systemd=no \
--enable-experimental
make
}
@@ -70,5 +72,5 @@
install -Dm644 ${srcdir}/bluetooth.modprobe ${pkgdir}/usr/lib/modprobe.d/bluetooth-usb.conf
# fix obex file transfer - https://bugs.archlinux.org/task/45816
- ln -fs /usr/lib/systemd/user/obex.service ${pkgdir}/usr/lib/systemd/user/dbus-org.bluez.obex.service
+# ln -fs /usr/lib/systemd/user/obex.service ${pkgdir}/usr/lib/systemd/user/dbus-org.bluez.obex.service
}
============================================================================
Testsuite summary for bluez 5.45
============================================================================
# TOTAL: 25
# PASS: 25
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
I wanted to build it with the tests if possible, although any build would be an improvement over none. I hadn't noticed the check funtion . I can't test it either, I have 2 bluetooth chips but no bluetooth devices.
If the tests complete there is a good chance the built package should work properly given the details on the bug report, also see the recent comment here:
https://aur.archlinux.org/packages/bluez-utils-compat/
Rebuilding all the bluez things with an older gcc version should hopefully fix the bluetooth problems.
Also you need an older gcc to build Pale Moon and gcc54 stopped getting updates last year and it was about time I got a newer version, but I'd been avoiding it as there are no alternative gcc binary packages any more. I mounted another partition with more space and changed the build dir in pakku.conf, thankfully that built with no errors as it took 2 or 3 hours on my hw.