Source: openvpn-auth-ldap
Version: 2.0.3-1
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> gcc -o testplugin testplugin.o -export-dynamic -L. -lauth-ldap-testing -lldap 
> -llber -lobjc 
> ./libauth-ldap-testing.a(auth-ldap.o): In function `find_ldap_group':
> /build/user-openvpn-auth-ldap_2.0.3-1-amd64-PKSooJ/openvpn-auth-ldap-2.0.3/src/auth-ldap.m:418:
>  undefined reference to `objc_msgSend'
> /build/user-openvpn-auth-ldap_2.0.3-1-amd64-PKSooJ/openvpn-auth-ldap-2.0.3/src/auth-ldap.m:418:
>  undefined reference to `objc_msgSend'
> /build/user-openvpn-auth-ldap_2.0.3-1-amd64-PKSooJ/openvpn-auth-ldap-2.0.3/src/auth-ldap.m:419:
>  undefined reference to `objc_msgSend'
> /build/user-openvpn-auth-ldap_2.0.3-1-amd64-PKSooJ/openvpn-auth-ldap-2.0.3/src/auth-ldap.m:424:
>  undefined reference to `objc_msgSend'
> /build/user-openvpn-auth-ldap_2.0.3-1-amd64-PKSooJ/openvpn-auth-ldap-2.0.3/src/auth-ldap.m:424:
>  undefined reference to `objc_msgSend'
> ./libauth-ldap-testing.a(auth-ldap.o):/build/user-openvpn-auth-ldap_2.0.3-1-amd64-PKSooJ/openvpn-auth-ldap-2.0.3/src/auth-ldap.m:421:
>  more undefined references to `objc_msgSend' follow
> collect2: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/05/02/openvpn-auth-ldap_2.0.3-1_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to