On 2018-05-02 04:07 PM, Lucas Nussbaum wrote: > Source: ust > Version: 2.10.1-2 > Severity: serious > Tags: buster sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20180502 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part (hopefully): >> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. >> -I../include/lttng -I../include -I../include >> -I/usr/lib/jvm/default-java/include >> -I/usr/lib/jvm/default-java/include/linux -Wdate-time -D_FORTIFY_SOURCE=2 >> -Wall -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong >> -Wformat -Werror=format-security -c -o LTTngUst.lo LTTngUst.c >> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include/lttng >> -I../include -I../include -I/usr/lib/jvm/default-java/include >> -I/usr/lib/jvm/default-java/include/linux -Wdate-time -D_FORTIFY_SOURCE=2 >> -Wall -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong >> -Wformat -Werror=format-security -c LTTngUst.c -fPIC -DPIC -o >> .libs/LTTngUst.o >> LTTngUst.c:20:10: fatal error: org_lttng_ust_LTTngUst.h: No such file or >> directory >> #include "org_lttng_ust_LTTngUst.h" >> ^~~~~~~~~~~~~~~~~~~~~~~~~~ >> compilation terminated. >> make[4]: *** [Makefile:501: LTTngUst.lo] Error 1 > > The full build log is available from: > http://aws-logs.debian.net/2018/05/02/ust_2.10.1-2_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. >
Hi, That's surprising, I did a source upload a week or so ago that built fine on the buildds. Looking at both build logs the difference seems to be that the default jdk changed from 9 to 10. I'll try to reproduce the failure on my system and fix it. Thanks for the heads up, Michael
