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


When the windows build fails, the real error is often hidden pretty far up the log.
That error message probably indicates that some earlier stage failed to link that file.

Kohei Yoshida wrote:
I've been trying to build master on Windows with MSVC, and could use some help.

Multiple git pull -r, and multiple clean builds over the past several
days, and my build always fails in desktop with the following message:

(lots of WARN prior to this similar to the one below)

/cygdrive/c/libo/core-master/desktop/Executable_unopkg.mk:41:
[ WARN   ] !!!
[ WARN   ] !!! desktop/win32/source/extendloaderenvironment is linked
in by  Executable/soffice.exe Executable/unopkg.exe
[ WARN   ] !!!
[ build DEP ] SRS:deployment/res
[ build SRS ] deployment/res
[ build DEP ] SRS:deploymentgui/res
[ build SRS ] deploymentgui/res
[ build DEP ] SRS:dkt/res
[ build SRS ] dkt/res
[ build LNK ] Executable/soffice_bin.exe
C:/libo/core-master/solenv/gbuild/Package.mk:33: ***
gb_Deliver_deliver: file does not exist in solver, and cannot be
delivered: /cygdrive/c/libo/core-master/solver/wntmsci12.pro/bin/soffice_bin.exe.manifest.
 Stop.

Anyone has any clue off the top of your head as to what could be going
wrong here?

TIA,

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


Disclaimer: http://www.peralex.com/disclaimer.html



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.