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


On 16/08/18 08:47, Stephan Bergmann wrote:
On 16/08/18 05:50, Ch g wrote:
autogen.input:

--enable-dbgutil
#--enable-debug
--disable-ccache
#--disable-cve-tests
--with-jdk-home=/Library/Java/JavaVirtualMachines/jdk-10.0.2.jdk/Contents/Home
--with-ant-home=/usr/local/Cellar/ant/1.10.5/libexec
--without-junit
--without-help
--without-myspell-dicts
--without-doxygen
--with-build-version=$(date +"Mac%Y-%m-%d")
--with-distro=LibreOfficeMacOSX
--with-package-format=dmg

command used:

make clean && ./autogen.sh && make -j 4 build-nocheck 2>&1

(I always get CppUnitTest errors without "build-nocheck" for both macos 10.13 and ubuntu 16.04.5/18.04.1)


Is "make" with "--with-distro=LibreOfficeMacOSX" and "--with-package-format=dmg" the correct way to create LO installation dmg file?

Your setup looks correct; beats me why it's failing for you that way. (I haven't built macOS packages myself in a while, but can check tonight whether any general error has sneaked in there lately.)

Cannot reproduce this (with configure settings not identical but somewhat comparable to yours; what I had to do was manually bump the -megabytes 1500 to 2000 in the hdiutil call in solenv/bin/modules/installer/simplepackage.pm, to avoid "hdiutil: create failed - No space left on device" errors).

If yours wasn't a from-scratch build, what might help is `make clean`.

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.