On fre, 2011-10-14 at 11:55 +0200, Jonas Smedegaard wrote: > > When I build this package in testing, I get this: > > > > ... > > gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../include > > "-D_U_=__attribute__((unused))" -g -O2 -fstack-protector > > --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security > > -Werror=format-security -Wall -fPIE -fstack-protector --param > > ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security > > -Werror=format-security -I../../sys -c uuid.c -fPIC -DPIC -o .libs/uuid.o > > gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../include > > "-D_U_=__attribute__((unused))" -g -O2 -fstack-protector > > --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security > > -Werror=format-security -Wall -fPIE -fstack-protector --param > > ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security > > -Werror=format-security -I../../sys -c uuid.c -o uuid.o >/dev/null 2>&1 > > /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 > > -DHAVE_CONFIG_H -I. -I../.. -I../../include > > -D_U_="__attribute__((unused))" -g -O2 -fstack-protector > > --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security > > -Werror=format-security -Wall -fPIE -fstack-protector --param > > ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security > > -Werror=format-security -I../../sys -c -o ldap.lo ldap.c > > gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../include > > "-D_U_=__attribute__((unused))" -g -O2 -fstack-protector > > --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security > > -Werror=format-security -Wall -fPIE -fstack-protector --param > > ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security > > -Werror=format-security -I../../sys -c ldap.c -fPIC -DPIC -o .libs/ldap.o > > ldap.c:56:18: error: array type has incomplete element type > > ldap.c:72:19: error: array type has incomplete element type > > make[4]: *** [ldap.lo] Error 1 > > make[4]: Leaving directory `/work/netatalk-2.2~beta4/libatalk/acl' > > make[3]: *** [all-recursive] Error 1 > > make[3]: Leaving directory `/work/netatalk-2.2~beta4/libatalk' > > make[2]: *** [all-recursive] Error 1 > > make[2]: Leaving directory `/work/netatalk-2.2~beta4' > > make[1]: *** [all] Error 2 > > make[1]: Leaving directory `/work/netatalk-2.2~beta4' > > make: *** [debian/stamp-makefile-build] Error 2 > > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > > > > In unstable, in a cowbuilder environment, it builds fine. > > > > Maybe this is some kind of transition issue and it'd be best to wait it > > out. > > But maybe in fact, a build dependency needs to be tightened or something, > > so I > > figured I'd better point it out.
> Since it built fine earlier on and does again now in unstable, I would > assume it is not a dependency being too old but some specific version of > e.g. libldap or gcc that is in the middle of a transition e.g. towards > proper handling of security flags. This problem still exists in current testing. > Did you test in a clean cowbuilder testing environment? No, I built it on my desktop, but that should work, too. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
