Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5.38, 10.0.12
Description
TokuDB does no longer build after some of it's build dependencies got updated in Debian unstable.
More details at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753222
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 same is now confirmed at http://buildbot.askmonty.org/buildbot/builders/debpkg-sid where the only difference between builds #26 and #27 is that a 'apt-get upgrade' was run in between, so indeed some new package in Debian unstable breaks the build process.
See full log at:
http://buildbot.askmonty.org/buildbot/builders/debpkg-sid/builds/27/steps/compile/logs/stdio
