On Sat, Jan 28, 2017 at 09:30:20AM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
> > /bin/bash ../libtool --tag=CC --mode=link x86_64-linux-gnu-gcc -Wall
> > -Werror -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=.
> > -fstack-protector-strong -Wformat -Werror=format-security -Wall
> > -Wno-error=deprecated-declarations -module -avoid-version
> > -export-symbols-regex '\<module_register\>' -Wl,-z,relro -o notify_email.la
> > -rpath /usr/lib/collectd notify_email.lo -lesmtp -lssl -lcrypto
> > libtool: link: /usr/bin/x86_64-linux-gnu-nm -B .libs/notify_email.o |
> > sed -n -e 's/^.*[ ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][
> > ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | sed '/ __gnu_lto/d' | /bin/sed
> > 's/.* //' | sort | uniq > .libs/notify_email.exp
> > libtool: link: /bin/grep -E -e "\<module_register\>"
> > ".libs/notify_email.exp" > ".libs/notify_email.expT"
> > libtool: link: mv -f ".libs/notify_email.expT" ".libs/notify_email.exp"
> > libtool: link: echo "{ global:" > .libs/notify_email.ver
> > libtool: link: cat .libs/notify_email.exp | sed -e "s/\(.*\)/\1;/" >>
> > .libs/notify_email.ver
> > libtool: link: echo "local: *; };" >> .libs/notify_email.ver
> > libtool: link: x86_64-linux-gnu-gcc -shared -fPIC -DPIC
> > .libs/notify_email.o -lesmtp -lssl -lcrypto -g -O2
> > -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-soname -Wl,notify_email.so
> > -Wl,-version-script -Wl,.libs/notify_email.ver -o .libs/notify_email.so
> > /usr/bin/ld: cannot find -lssl
> > /usr/bin/ld: cannot find -lcrypto
> > collect2: error: ld returned 1 exit status
>
> The full build log is available from:
> http://aws-logs.debian.net/2017/01/28/collectd_5.7.1-1_unstable.log
Nice catch, thanks !
One thing that puzzles me, is why didn't this pop up earlier. collectd does
*not* build-depend on libssl-dev. But according to the latest build log[1]
libssl1.0-dev gets installed nevertheless (making this mistake in
collectd's Makefile work by accident). This is not the case on the
AWS-based builder.
There seems to be some discrepancy between the official builders and the
AWS one (the latter being correct/stricter).
Cheers,
Marc
[1]
https://buildd.debian.org/status/fetch.php?pkg=collectd&arch=amd64&ver=5.7.1-1&stamp=1485207190&raw=0
