Hi everyone,
Am 04.06.19 um 17:01 schrieb Luke Benes:
The decision was to demote release builds, but NOT to remove x86
compatibility. If you take this as an excuse to also end x86 CI testing bots,
you are effectively killing x86 through bit rot. This is not a hypothetical.
As you know, @87 just recently caught a regression introduced by an easyHack
to convert use of sal_uLong to better integer types. Without CI testing,
these bugs will pile up effectively removing x86 compatibility.
IMHO we should "just" switch one of the Jenkins Linux builds to 32bit, not have
an other one. Preferable the gcc release one, as that has smaller object size,
if that is a concern for 32bit (linking etc). Should be fine just to cross-build
on 64bit in a 32bit chroot.
I remember there were some problems because of a missing 32bit Red Hat Developer
Toolset needed for the build, which was AFAIK the real reason to get rid of the
32bit builds - aehmm. Not sure that is now available.
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.