c2216d2d7a
...which was at maximum set to GCC's -finline-limit=0 -fno-inline (solenv/gbuild/platform/com_GCC_defs.mk). Those options were set for debug builds "since forever", but that looks very much like cargo cult: -fno-inline "is the default when not optimizing" anyway (<https://gcc.gnu.org/onlinedocs/gcc-7.4.0/gcc/Optimize-Options.html>), and it is unclear to me how -finline-limit=0 should have any impact beyond -fno-inline (and maybe was present for ancient compilers that only supported -finline-limit but not -fno-inline?). Change-Id: Id6752d03b1b7ec8763defabc5720d4dd08790874 Reviewed-on: https://gerrit.libreoffice.org/66836 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com> |
||
|---|---|---|
| .. | ||
| clang-cl.patch.0 | ||
| ExternalPackage_liblangtag.mk | ||
| ExternalPackage_liblangtag_data.mk | ||
| ExternalProject_liblangtag.mk | ||
| langtag-libtool-rpath.patch.0 | ||
| langtag-valencia.patch.0 | ||
| liblangtag-bundled-soname.patch.0 | ||
| Makefile | ||
| Module_liblangtag.mk | ||
| README | ||
| UnpackedTarball_liblangtag.mk | ||
From [http://tagoh.bitbucket.org/liblangtag/]. An interface for BCP47 language tags. Updated IANA Language Subtag Registry files are available as [https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry] and per convention are stored as a data/language-subtag-registry file in a language-subtag-registry-YYYY-MM-DD.tar.bz2 archive, with YYYY-MM-DD being the File-Date entry of the file, for example language-subtag-registry-2015-08-04.tar.bz2, and uploaded to the external sources repository to be included in the build of liblangtag. See download.lst LANGTAGREG_TARBALL and LANGTAGREG_SHA256SUM.