Date: prev next · Thread: first prev next last
2020 Archives by date, by thread · List index


Thanks.
There is a difference in how I invoke the build.
LO: '--enable-dbgutil --disable-symbols --disable-64-bit
--disable-dependency-tracking
--srcdir=/home/tdf/lode/jenkins/workspace/gerrit_windows
--enable-option-checking=fatal'
Me:--with-external-tar=/path --with-junit=/path --with-ant-home=/path
--enable-pch --disable-ccache --enable-release-build --enable-64-bit
--disable-dependency-tracking --with-visual-studio=2019
--with-jdk-home="/cygdrive/c/Program Files/AdoptOpenJDK/jdk-11-hotspot"

The SSL DLL errors are from the tar files related to external
tar openssl-1.0.2t.tar.gz.
I was going with options mentioned on
https://wiki.documentfoundation.org/Development/BuildingOnWindows
If I don't specify  --with-external-tar, do I need to install more stuff?
Where can I find more documentation on that?

On Tue, Jun 9, 2020 at 12:24 PM Michael Weghorn <m.weghorn@posteo.de> wrote:

On 09/06/2020 08.40, Chetan Aru wrote:
I have been asked to produce a build from any of the tags 6.4.3.x or
later.
So looks like my best bet is wait for 6.4.5.x or figure out a way to get
around the build error.

In case you really don't have the option to add that commit for some
reason or wait until 6.4.5 has been tagged, the build log of the Jenkins
build of the parent commit (i.e. which doesn't contain the fix) might
help to see what's the relevant difference in your setup (since this one
worked while yours fails):

https://ci.libreoffice.org/job/gerrit_windows/65734/consoleFull


Context


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.