Package Details: lib32-bluez 5.40-1

Git Clone URL: https://aur.archlinux.org/lib32-bluez.git (read-only)
Package Base: lib32-bluez
Description: Daemons for the bluetooth protocol stack (32-bit)
Upstream URL: http://www.bluez.org/
Licenses: GPL2
Submitter: rafaelff
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 10
Popularity: 2.114473
First Submitted: 2012-11-02 21:08
Last Updated: 2016-06-29 01:29

Pinned Comments

WoefulDerelict commented on 2016-05-15 19:43

Users should be aware this package has a PGP signature for the source which is separate from the Arch Linux keyring. Please see this helpful article by one of Arch Linux's developer's here: http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

There are instructions on how to use a keyserver to import keys and how to automate the retrieval process here: https://wiki.archlinux.org/index.php/GnuPG#Use_a_keyserver

To quickly import the necessary key via its fingerprint execute the following:
gpg --recv-keys 1DCF2659

Latest Comments

WoefulDerelict commented on 2016-05-19 01:11

oi_wtf: It's what I'm here for. Glad it is working for you as well.

oi_wtf commented on 2016-05-19 00:27

thanks. build works now.

WoefulDerelict commented on 2016-05-18 20:10

It appears as though I've located the missing dependencies and included them where appropriate. I am able to build this package in an initial pacstrap of base and base-devel after enabling multilib to satisfy dependencies from the repo and building lib32-libical. I'll have the package updated shortly.

UPDATE: All my local build tests are complete and the updated package is now live. Good luck.

WoefulDerelict commented on 2016-05-18 01:41

I will take a look at this in a clean environment and see if I can't track down the issue you're experiencing. Our builds definitely diverge rather early in the process; however, I'm unsure if this is due to missing dependencies or something less transparent. While our configure outputs are identical your build is reaching profiles/sap/bluetoothd-sap-dummy.o and crashing quite early where as on my local system it builds a great many other pieces before reaching the same point. It is possible it is skipping those components because of a missing dependency. It is just as likely to be something else simple as well or a complicated mess neither of us has imagined yet.

If you could edit the PKGBUILD to disable parallel building by suffixing the make command in build() with -j1 I'd appreciate the additional test data to eliminate other possibilities.

EDIT: I seem to have produced a complaint about something missing by the linker in one test. Investigating further.

I've succeeded in reproducing the error and generated an identical build output. I'll see if I can't track down what is broken or missing and get it mended. Thanks for finding the issue.

UPDATE: As this package is derived from the bluez split package in the extra repo I'm going to investigate to see if the error is shared between them.

RESULTS: As I expected bluez from the extra repos builds just fine. This is likely because all of its requirements are met by a basic pacstrap of base and base-devel. I suspect this will narrow my search quite a bit to one of the core glibc components in lib32 that isn't getting pulled in but should likely exist before building any lib32 package.

oi_wtf commented on 2016-05-17 23:33

It fails to build in a clean chroot.
Probably because some dependency is missing.
Could you look into it?

Buildlog: https://ptpb.pw/g1QB

WoefulDerelict commented on 2016-05-15 19:43

Users should be aware this package has a PGP signature for the source which is separate from the Arch Linux keyring. Please see this helpful article by one of Arch Linux's developer's here: http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

There are instructions on how to use a keyserver to import keys and how to automate the retrieval process here: https://wiki.archlinux.org/index.php/GnuPG#Use_a_keyserver

To quickly import the necessary key via its fingerprint execute the following:
gpg --recv-keys 1DCF2659