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


Hi Matúš,

Matúš Kukan schrieb:
On 27 October 2012 09:25, Regina Henschel <rb.henschel@t-online.de> wrote:
Hi all,

I tried to build LO with MSVC on WinXP, but building fails somewhere in the
end. I have attached the file build_error.log.


: ERROR: Removing file shared_en-US.zip from file list.
: ERROR: Removing file sbasic_en-US.zip from file list.
: ERROR: Removing file scalc_en-US.zip from file list.
: ERROR: Removing file schart_en-US.zip from file list.
: ERROR: Removing file sdatabase_en-US.zip from file list.
: ERROR: Removing file sdraw_en-US.zip from file list.
: ERROR: Removing file simpress_en-US.zip from file list.
: ERROR: Removing file smath_en-US.zip from file list.
: ERROR: Removing file swriter_en-US.zip from file list.

means you don't have helpcontent2 built and delivered.
No idea why.

I find error message in the fetch log:
Cloning into helpcontent2...
fatal: reference is not a tree: 2cc7764943882fa89e31c96f6e0467c96bda3976
Unable to checkout '2cc7764943882fa89e31c96f6e0467c96bda3976' in submodule path 'helpcontent2'

And indeed folder helpcontent2 exists but is empty besides subfolder .git.

Either ensure that make helpcontent2.deliver does something or
add --without-help to autogen.lastrun; make scp2.clean and make again

Trying 'make fetch' again gives only:
make[1]: Nothing to be done for `fetch'.

How to get helpcontent2 afterwards?

Kind regards
Regina

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.