This error rings a faint bell, but I believe it was a problem with my toolchain, not a bug in the code or build system. There are also sometimes dependency problems with cmake that building with -j1 can fix. Can you reproduce it multiple times in a row with the same configured build directory? Can you reproduce it without using parallel make? If both of those are true, can you build again with VERBOSE=1 and post the log, as well as objdump the symbols defined in libtokuportability_static.a? On Wed, Jul 9, 2014 at 7:57 AM, Otto Kekäläinen <otto@seravo.fi> wrote:
Hello Rich!
For some strange reason, re-building 5.5.37 in Debian unstable stopped working.
Any ideas what might be going on here?: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753222
Recently a build of 5.5.38 generated a similar error: http://paste.ubuntu.com/7747594/
Are these maybe related?
I have no idea how to fix these apart from disabling TokuDB in Debian when uploading 5.5.38.
-- Check out our blog at http://seravo.fi/blog and follow @ottokekalainen
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
-- Cheers, Leif