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


Perhaps add a link to a pastebin instead of sending the build.log. 

Chris

On 3 Jan 2016, at 7:21 AM, Jan Rheinländer <jrheinlaender@gmx.de> wrote:

Hi,

I tried building the branch libreoffice-5-0-4 on Windows, following the
LODE instructions, and got:

....
[build RC ] cppu/default
[build RC ] cppuhelper/default
[build RC ] xmlreader/default
[build C  ] cppuhelper/source/findsofficepath.c
[build RC ] ucbhelper/default
[build RC ] i18nlangtag/default
[build RC ] tl/default
[build RC ] basegfx/default
[build RC ] sax/default
Die Eingabedatei wurde zweimal angegeben.             <<<=== The input
file was mentioned twice (my translation)

C:/Users/User/Documents/lode/dev/core/solenv/gbuild/UIConfig.mk:186:
recipe for target
'C:/Users/User/Documents/lode/dev/core/workdir/UIConfig/modules/dbapp.ilst'
failed
make[1]: ***
[C:/Users/User/Documents/lode/dev/core/workdir/UIConfig/modules/dbapp.ilst]
Error 1
make[1]: *** Deleting file
'C:/Users/User/Documents/lode/dev/core/workdir/UIConfig/modules/dbapp.ilst'
make[1]: *** Waiting for unfinished jobs....
Makefile:250: recipe for target 'build' failed
make: *** [build] Error 2

What's wrong?

If allowed on this list, I can attach the complete build.log file.

Jan Rheinländer

_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


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.