Hi, Starting with 3.6 branch and addition of loads of unittests that are executed during the build (which i still consider really bad idea) the build fails whenever some of these configure switches are passed: --disable-graphlite --disable-xmlsec Reason is that the unittests are executed every time. I am not posting the actual crashers as you can trigger them easily by just passing the configure option. I suppose we could start one additional tinderbox called "Minimal one" which would build with everything possible disabled to avoid this in future? Cheers Tom
Tomáš: I noticed this commit http://cgit.freedesktop.org/libreoffice/core/commit/?id=ee93dfafddd0f14b9a1ac3c82b967bf3a65f64aa which removed --disable-xmlsec but --disable-graphite is still there. Do you still have building problem with the last one?
Well I am not sure how to proceed. Now the failures are not in the actual code but the tests are run and fail if you build without graphlite.
Hi Tomáš, this is quite an old bug. Have you retried this with newer version of LO? Are the issues you had building LO still persisting?
Yep this is still present. The build issues are fixed. But if you try to run make check or unitcheck/etc the testsuite will fail because it tries to run checks for the code that was actually disabled during configure.
Bug does not meet the criteria for Status 'REOPENED' https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/REOPENED#Criteria Status -> NEW
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
The problem is still present. Simply put all unittests are run even if feature is disabled by configure.
The two originally mentioned configure options --disable-graphite and --disable-xmlsec no longer exist. So the specific initial issue doesn't exist. There are quite likely combinations of configure options that don't build. We do now have a "random config" tinderbox that tries all combinations, i.e. https://ci.libreoffice.org/job/lo_tb_random_config_linux/ to try and flush those out.