[debian-mysql] Bug#753222: mariadb-5.5: FTBFS: logformat.cc:847: undefined reference to `toku_do_assert_fail(char const*, char const*, char const*, int, int)'

[David Suárez]

Source: mariadb-5.5
Version: 5.5.37-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140628 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):
> [ 56%] Building CXX object storage/tokudb/ft-index/ft/CMakeFiles/logformat.dir/logformat.cc.o
> Linking CXX executable logformat
> /tmp/ccGSgbuE.ltrans0.ltrans.o: In function `main':
> /«PKGBUILDDIR»/storage/tokudb/ft-index/ft/logformat.cc:847: undefined reference to `toku_do_assert_fail(char const*, char const*, char const*, int, int)'
> /tmp/ccGSgbuE.ltrans0.ltrans.o: In function `get_error_errno':
> /«PKGBUILDDIR»/storage/tokudb/ft-index/toku_include/toku_assert.h:191: undefined reference to `toku_do_assert_fail(char const*, char const*, char const*, int, int)'
> /tmp/ccGSgbuE.ltrans0.ltrans.o: In function `main':
> /«PKGBUILDDIR»/storage/tokudb/ft-index/ft/logformat.cc:840: undefined reference to `toku_do_assert_fail(char const*, char const*, char const*, int, int)'
> /«PKGBUILDDIR»/storage/tokudb/ft-index/ft/logformat.cc:839: undefined reference to `toku_do_assert_fail(char const*, char const*, char const*, int, int)'
> /«PKGBUILDDIR»/storage/tokudb/ft-index/ft/logformat.cc:838: undefined reference to `toku_do_assert_fail(char const*, char const*, char const*, int, int)'
> /tmp/ccGSgbuE.ltrans0.ltrans.o:/«PKGBUILDDIR»/storage/tokudb/ft-index/ft/logformat.cc:830: more undefined references to `toku_do_assert_fail(char const*, char const*, char const*, int, int)' follow
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/06/28/mariadb-5.5_5.5.37-1_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.