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


Julien, try excluding the source and workdir folders from your anti-virus
software (or Microsoft Security Essentials) as well as the root of cygwin
directory.

It's known that anti-virus both locks files and arbitrarily fails process
spawning and forking, and cause random build failures (especially unittest
failures).

Next, find a commit that Jankins built without error and check it out.
Clean build.


On Mon, Aug 17, 2015 at 3:40 PM, julien2412 <serval2412@yahoo.fr> wrote:

Michael Stahl-2 wrote
On 16.08.2015 10:13, julien2412 wrote:
I updated my local repo (still master sources), I still get the same.

what does this say

find workdir/UnpackedTarball/nss -name nspr4.lib

perhaps the build of nss failed, and the
workdir/UnpackedTarball/nss/nss/build.log has some details?

$ find workdir/UnpackedTarball/nss -name nspr4.lib
workdir/UnpackedTarball/nss/nspr/out/pr/src/nspr4.lib

Here's the build log of nss:
build_nss_log.txt
<http://nabble.documentfoundation.org/file/n4157542/build_nss_log.txt>

Julien



--
View this message in context:
http://nabble.documentfoundation.org/Fail-to-build-on-Windows-7-32-bits-tp4156056p4157542.html
Sent from the Dev mailing list archive at Nabble.com.
_______________________________________________
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.