Problem description: When building LibreOffice 3.6.1.2, build fails w/ the following: ----------------------------------------------------------------------- Oh dear - something failed during the build - sorry ! For more help with debugging build errors, please see the section in: http://wiki.documentfoundation.org/Development internal build errors: ERROR: error 512 occurred while making /tmp/portage/app-office/libreoffice-3.6.1.2/work/libreoffice-core-3.6.1.2/tail_build/prj it seems that the error is inside 'tail_build', please re-run build inside this module to isolate the error and/or test your fix: build_error.log should contain the captured output of the failed module(s) ----------------------------------------------------------------------- The corresponding error is: [ build CXX ] sfx2/source/appl/app.cxx tests.cxx:132:Assertion Test name: (anonymous namespace)::PDFITest::testXPDFParser assertion failed - Expression: rtl::math::approxEqual(m_aHyperlinkBounds.X1,34.7 ) && rtl::math: :approxEqual(m_aHyperlinkBounds.Y1,386.0) && rtl::math::approxEqual(m_aHyperlin kBounds.X2,166.7) && rtl::math::approxEqual(m_aHyperlinkBounds.Y2,406.2) - Correct hyperlink bounding box Failures !!! Run: 3 Failure total: 1 Failures: 1 Errors: 0 Error: a unit test failed, please do one of: export DEBUGCPPUNIT=TRUE # for exception catching export GDBCPPUNITTRACE="gdb --args" # for interactive debugging export VALGRIND=memcheck # for memory checking and retry. This failure seems to be similar w/ one described at http://lists.freedesktop.org/archives/libreoffice/2012-March/027790.html. Steps to reproduce: Try to build LibreOffice w/ pdfimport extension Current behavior: Build failure Expected behavior: Successful build Platform (if different from the browser): GNU/Linux x86_64
Hopefully workaround from a9b7c8ba65d74d7ee5fef2750ae9e81945b9e1e3 works for me.
Indeed it does.
I'm assuming that means this is solved, and am therefore closing the bug.
(In reply to comment #3) > I'm assuming that means this is solved, and am therefore closing the bug. It means that there's at least a workaround in master, and that 3.6 had to be manually patched two weeks ago w/ possible loss of a couple of tests. It's up to developers to ensure that this is solved and that real fix is backported to the next 3.6.x.