bluez-tools FTBFS on wily-proposed due to AM_LDFLAGS misuse
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez-tools (Debian) |
Fix Released
|
Unknown
|
|||
bluez-tools (Ubuntu) |
Fix Released
|
Undecided
|
Mathieu Trudel-Lapierre |
Bug Description
bluez-tools FTBFS in wily-proposed with the following error:
gcc -g -O2 -fstack-
lib/agent-helper.o: In function `_find_device_pin':
/«PKGBUILDDIR»
/«PKGBUILDDIR»
<snip>
/«PKGBUILDDIR»
/«PKGBUILDDIR»
/«PKGBUILDDIR»
collect2: error: ld returned 1 exit status
make[3]: *** [bt-adapter] Error 1
Makefile:574: recipe for target 'bt-adapter' failed
make[3]: Leaving directory '/«PKGBUILDDIR»
make[2]: *** [all-recursive] Error 1
Makefile:362: recipe for target 'all-recursive' failed
make[2]: Leaving directory '/«PKGBUILDDIR»'
make[1]: *** [all] Error 2
Makefile:303: recipe for target 'all' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
debian/rules:8: recipe for target 'build' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2
This is due to the libraries being set in LDFLAGS while they should actually be set on LIBS or LDADD [1,2].
[1] http://
[2] http://
summary: |
- bluez-tools FTBFS on wily-proposed + bluez-tools FTBFS on wily-proposed due to LDFLAGS misuse |
summary: |
- bluez-tools FTBFS on wily-proposed due to LDFLAGS misuse + bluez-tools FTBFS on wily-proposed due to AM_LDFLAGS misuse |
description: | updated |
Changed in bluez-tools (Debian): | |
status: | Unknown → New |
Changed in bluez-tools (Debian): | |
status: | New → Fix Released |
Sponsoring this...