Package Details: bluez-utils-compat 5.50-3

Git Clone URL: https://aur.archlinux.org/bluez-utils-compat.git (read-only)
Package Base: bluez-utils-compat
Description: Development and debugging utilities for the bluetooth protocol stack. Includes deprecated tools.
Upstream URL: http://www.bluez.org/
Keywords: hciconfig hcidump hcitool
Licenses: GPL2
Conflicts: bluez-hcidump, bluez-hcitool, bluez-utils
Provides: bluez-hcidump, bluez-utils
Replaces: bluez<=4.101, bluez-hcidump
Submitter: thurstylark
Maintainer: twa022
Last Packager: twa022
Votes: 25
Popularity: 1.884627
First Submitted: 2017-03-02 17:34
Last Updated: 2019-01-16 02:37

Required by (30)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

NicolasV commented on 2017-05-10 22:36

I made a diff of the configure step on my laptop (ok) and my desktop (ko)
Here's the result of the diff. The only difference seems to be the paths : /usr/sbin (on my laptop) /usr/bin (on my desktop) but I don't think that's the cause of the problem.


diff --color configure_*
3c3
< checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
---
> checking for a thread-safe mkdir -p... /usr/sbin/mkdir -p
21,22c21,22
< checking for grep that handles long lines and -e... /usr/bin/grep
< checking for egrep... /usr/bin/grep -E
---
> checking for grep that handles long lines and -e... /usr/sbin/grep
> checking for egrep... /usr/sbin/grep -E
39c39
< checking for pkg-config... /usr/bin/pkg-config
---
> checking for pkg-config... /usr/sbin/pkg-config
52,57c52,57
< checking for a sed that does not truncate output... /usr/bin/sed
< checking for fgrep... /usr/bin/grep -F
< checking for ld used by gcc... /usr/bin/ld
< checking if the linker (/usr/bin/ld) is GNU ld... yes
< checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
< checking the name lister (/usr/bin/nm -B) interface... BSD nm
---
> checking for a sed that does not truncate output... /usr/sbin/sed
> checking for fgrep... /usr/sbin/grep -F
> checking for ld used by gcc... /usr/sbin/ld
> checking if the linker (/usr/sbin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/sbin/nm -B
> checking the name lister (/usr/sbin/nm -B) interface... BSD nm
64c64
< checking for /usr/bin/ld option to reload object files... -r
---
> checking for /usr/sbin/ld option to reload object files... -r
73c73
< checking command to parse /usr/bin/nm -B output from gcc object... ok
---
> checking command to parse /usr/sbin/nm -B output from gcc object... ok
85c85
< checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
---
> checking whether the gcc linker (/usr/sbin/ld -m elf_x86_64) supports shared libraries... yes

NicolasV commented on 2017-05-10 15:27

Too long to paste.
Here's a link to check the log file, which seems incomplete.
Last line is just half-written...

http://www.wepaste.com/bluez-utils-compat/

thurstylark commented on 2017-05-10 14:58

Post the contents of the resulting test-suite.log

NicolasV commented on 2017-05-10 11:23

Same error, here is the full trace:
[...]
PASS: unit/test-textfile
PASS: unit/test-ecc
PASS: unit/test-avctp
PASS: unit/test-gobex-transfer
PASS: unit/test-avdtp
PASS: unit/test-avrcp
./test-driver: line 107: 19399 Segmentation fault (core dumped) "$@" > $log_file 2>&1
FAIL: unit/test-gatt
make --no-print-directory all-am
============================================================================
Testsuite summary for bluez 5.45
============================================================================
# TOTAL: 25
# PASS: 24
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
============================================================================
See ./test-suite.log
============================================================================
make[3]: *** [Makefile:8493: test-suite.log] Error 1
make[2]: *** [Makefile:8601: check-TESTS] Error 2
make[1]: *** [Makefile:8985: check-am] Error 2
make: *** [Makefile:8987: check] Error 2
==> ERROR: A failure occurred in check().
Aborting...
==> ERROR: Makepkg was unable to build bluez-utils-compat.
==> Restart building bluez-utils-compat ? [y/N]
==> -------------------------------------------
==>

framas commented on 2017-05-10 10:18

I've tested it with makechrootpkg in an clean enviroment. Does also not work

CCLD unit/test-gatt
./test-driver: line 107: 9621 Segmentation fault (core dumped) "$@" > $log_file 2>&1
FAIL: unit/test-gatt
make --no-print-directory all-am
make[5]: Nothing to be done for 'all-am'.
============================================================================
Testsuite summary for bluez 5.45
============================================================================
# TOTAL: 25
# PASS: 24
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
============================================================================
See ./test-suite.log
============================================================================
make[3]: *** [Makefile:8493: test-suite.log] Error 1
make[2]: *** [Makefile:8601: check-TESTS] Error 2
make[1]: *** [Makefile:8985: check-am] Error 2
make: *** [Makefile:8987: check] Error 2
==> ERROR: A failure occurred in check().
Aborting...
==> ERROR: Build failed, check /tmp/copy/build

thurstylark commented on 2017-05-09 17:37

I wasn't suggesting setting LANG=C as a fix, I suggested it so the output would be in English.

https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot

NicolasV commented on 2017-05-09 14:11

On May 5th I sucessfully upgraded this package on my laptop. I just can't upgrade on my main PC.
I also tried setting "LANG=C" while calling "yaourt -Syua" but luck.
Is there a simple method to build in a clean chroot?

thurstylark commented on 2017-05-09 13:07

@nicolasvila Can you try the build again with LANG=C?

Also, have you tried building in a clean chroot?

NicolasV commented on 2017-05-09 07:22

Latest version 5.45-1 crash during unit test:

[...]
PASS: unit/test-eir
PASS: unit/test-uuid
PASS: unit/test-textfile
PASS: unit/test-avctp
PASS: unit/test-avdtp
PASS: unit/test-gobex-transfer
PASS: unit/test-avrcp
./test-driver : ligne 107 : 9008 Erreur de segmentation (core dumped)"$@" > $log_file 2>&1
FAIL: unit/test-gatt
make --no-print-directory all-am
============================================================================
Testsuite summary for bluez 5.45
============================================================================
# TOTAL: 25
# PASS: 24
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
============================================================================
See ./test-suite.log
============================================================================
make[3]: *** [Makefile:8493: test-suite.log] Error 1
make[2]: *** [Makefile:8601: check-TESTS] Error 2
make[1]: *** [Makefile:8985: check-am] Error 2
make: *** [Makefile:8987: check] Error 2
==> ERREUR : Une erreur s’est produite dans check().
Abandon...
==> ERREUR : Makepkg n'a pas pu construire bluez-utils-compat.
==> Relancer la compilation de bluez-utils-compat ? [o/N]
==> -----------------------------------------------------
==>
==> ERREUR : impossible de mettre à jour

thurstylark commented on 2017-04-25 15:44

Builds in a clean chroot just fine for me.