office-gobmx/distro-configs
Stephan Bergmann c394e6a5c8 Clang ASan fails with gold
...for whatever reason.  Failure is

> AddressSanitizer:DEADLYSIGNAL
> =================================================================
> ==16438==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x2b6ba8bfe65c bp 0x7ffca100f290 sp 0x7ffca100ba28 T0)
> ==16438==The signal is caused by a READ memory access.
> ==16438==Hint: address points to the zero page.
>     #0 0x2b6ba8bfe65b  (<unknown module>)
>
> AddressSanitizer can not provide additional info.
> SUMMARY: AddressSanitizer: SEGV (<unknown module>)
> ==16438==ABORTING
> /home/tdf/lode/jenkins/workspace/lo_ubsan/testtools/CustomTarget_uno_test.mk:25: recipe for target '/home/tdf/lode/jenkins/workspace/lo_ubsan/workdir/CustomTarget/testtools/uno_test.done' failed

(<https://ci.libreoffice.org/job/lo_ubsan/1177/>, but also seen with local ASan+
UBSan builds.)

Started to fail with 98f5f97d4a "make --enable-ld
the default for debug builds, if available".  (lld would automatically be
disabled by configure.ac because it doesn't support --dynamic-list-cpp-typeinfo
as needed by UBSan.)

Change-Id: I7bfbfc4c879cbad7748e5855c22698eec5efc94c
2019-02-05 08:45:57 +01:00
..
Jenkins Clang ASan fails with gold 2019-02-05 08:45:57 +01:00
LibreOfficeAndroid.conf
LibreOfficeAndroidAarch64.conf
LibreOfficeAndroidX86.conf
LibreOfficeCoverity.conf
LibreOfficeFlatpak.conf aarch64 and arm need libatomic_ops 2019-01-28 12:38:41 +01:00
LibreOfficeHaiku.conf
LibreOfficeiOS.conf
LibreOfficeLinux.conf
LibreOfficeMacOSX.conf
LibreOfficeOpenBSD.conf
LibreOfficeOssFuzz.conf
LibreOfficeVanillaMacAppStore.conf
LibreOfficeWin32.conf
LibreOfficeWin64.conf
README

Pre-canned distribution configurations

These files are supposed to correspond to the options used when
creating the Document Foundation (or other "canonical") builds of
LibreOffice for various platforms. They are *not* supposed to
represent the "most useful" options for developers in general. On the
contrary, the intent is that just running ./autogen.sh without any
options at all should produce a buildable configuration for developers
with interest in working on the most commonly used parts of the code.

See [[https://wiki.documentfoundation.org/Development/ReleaseBuilds]] for how
TDF builds make use of these switches.  (Especially, since --with-package-format
now triggers whether or not installation sets are built, all the relevant *.conf
files specify it, except for LibreOfficeLinux.conf, where the TDF build
instructions pass an explicit --with-package-format="rpm deb" in addition to
--with-distro=LibreOfficeLinux.)

(Possibly the above is a misunderstanding, or maybe there never even
has been any clear consensus what situations these files actually are
intended for.)

The files contain sets of configuration parameters, and can be passed
on the autogen.sh command line thus:

./autogen.sh --with-distro=LibreOfficeFoo

Contrary to the above, in the Android case the amount of parameters
you just must use is so large, that for convenience it is always
easiest to use the corresponding distro-configs file. This is a bug
and needs to be fixed; also configuring for Android should ideally use
sane (or the only possible) defaults and work fine without any
parameters at all.