[pkg-lua-devel] Bug#713467: lua-ldap: FTBFS: ld: =?UTF-8?Q?/=C2=ABPKGBUILDDIR=C2=BB/5.1-ldap/.libs/liblua5.1-ldap.a?=(lualdap.o): undefined reference to symbol 'ber_free@@OPENLDAP_2.4_2'

[David Suárez]

Source: lua-ldap
Version: 1.1.0-1-geeac494-3
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Maybe you need to add explicitly the offending lib to LD flags.

Relevant part:
> 	/lib64/ld-linux-x86-64.so.2 (0x00002af02798a000)
> 	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00002af029882000)
> 	libtasn1.so.3 => /usr//lib/x86_64-linux-gnu/libtasn1.so.3 (0x00002af029a9b000)
> 	libp11-kit.so.0 => /usr//lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00002af029cac000)
> 	libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00002af029ecc000)
> ********************** app dynamic (5.1) *********
> SKIPPED!
> **************************************************
> libtool --silent --tag=CC --mode=link cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -I/usr//include/lua5.1    -Wall -Wextra -Wl,--no-add-needed \
> 		-static -o /«PKGBUILDDIR»/5.1-ldap/app-static -I . -I /«PKGBUILDDIR»/5.1-ldap/ \
> 		/usr/share/dh-lua/test/5.1/app.c /«PKGBUILDDIR»/5.1-ldap/liblua5.1-ldap.la \
> 		-Wl,-z,relro  -L/usr//lib -llua5.1 -lm -ldl  
> /usr/bin/ld: /«PKGBUILDDIR»/5.1-ldap/.libs/liblua5.1-ldap.a(lualdap.o): undefined reference to symbol 'ber_free@@OPENLDAP_2.4_2'
> /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2: error adding symbols: DSO missing from command line
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/lua-ldap_1.1.0-1-geeac494-3_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.