On Mon, 2012-05-28 at 22:15 +0200, Riccardo Magliocchetti wrote:
i have this test failures while building libo, i'm getting these while 
building headless so today tried to build libo without --enable-headless 
and got them too:
        FWIW, from a clean[1] build on my linux machine of master from
commit a26efd71ed18738edb6b4fe272418831e797dac6
        I get:
[ build CUT ] sw_filters_test
File tested,Test Result,Execution Time (ms)
file:///data/opt/libreoffice/master/sw/qa/core/data/xml/fail/CVE-2006-3117-1.sxw,Fail,153
File tested,Test Result,Execution Time (ms)
file:///data/opt/libreoffice/master/sw/qa/core/data/ww8/pass/CVE-2010-3454-1.doc.dc,Fail,27
filters-test.cxx:129:Assertion
Test name: SwFiltersTest::testCVEs
assertion failed
- Expression: bRes == (nExpected == test::pass)
- file:///data/opt/libreoffice/master/sw/qa/core/data/ww8/pass/CVE-2010-3454-1.
doc.dc
        I suspect this is something to do with this different block of
configure options I'm using vs. another identical system where it works
fine:
--disable-build-mozilla
--disable-mozilla
--with-system-nss
--enable-telepathy
--with-system-dicts
--without-myspell-dicts
        IMHO - it makes most sense for the unit tests to cut out those bits
that are known not to work for a given configuration - so the most
people can build straight through.
        Then again, it's rather unclear to me why any of the above should break
things (so perhaps it is something else).
        HTH,
                Michael.        
[1] - make clean ; rm -Rf workdir solver
-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot
Context
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.