Bug 53432 - Some configure switches result in broken build since 3.6 release
Summary: Some configure switches result in broken build since 3.6 release
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) All
: medium major
Assignee: Not Assigned
Keywords: regression
Depends on:
Reported: 2012-08-13 08:49 UTC by Tomáš Chvátal
Modified: 2017-03-24 12:39 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Tomáš Chvátal 2012-08-13 08:49:01 UTC

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:


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?


Comment 1 Julien Nabet 2014-02-01 14:38:08 UTC
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?
Comment 2 Tomáš Chvátal 2014-02-02 13:33:34 UTC
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.
Comment 3 steve 2015-04-16 07:18:56 UTC
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?
Comment 4 Tomáš Chvátal 2015-04-16 08:19:23 UTC
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.
Comment 5 Buovjaga 2015-10-09 18:02:35 UTC
Bug does not meet the criteria for Status 'REOPENED'
Status -> NEW
Comment 6 QA Administrators 2016-11-08 11:39:52 UTC Comment hidden (obsolete)
Comment 7 Tomáš Chvátal 2016-11-08 11:48:46 UTC
The problem is still present. Simply put all unittests are run even if feature is disabled by configure.
Comment 8 Caolán McNamara 2017-03-24 12:39:58 UTC
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.