Re: Fail to build on Windows 7 (32 bits)

On 19.08.2015 21:35, julien2412 wrote: > After having added some traces, here's what I got: > $CC = cl > $CC_VERSION is empty oh okay... so what does the command "${CC}" -v output when run from the configure script? either it can't find cl in path or the regex in there is wrong... does it help

Re: Fail to build on Windows 7 (32 bits)

After having added some traces, here's what I got: $CC = cl $CC_VERSION is empty -- View this message in context: http://nabble.documentfoundation.org/Fail-to-build-on-Windows-7-32-bits-tp4156056p4157705.html Sent from the Dev mailing list archive at Nabble.com.

Re: Fail to build on Windows 7 (32 bits)

Michael Stahl-2 wrote > ... > can you patch in an echo around the CC_VERSION=`"${CC}" ... line to see > what the value of $CC and $CC_VERSION is? I'll give a try after my day time job but if I do this, it means I should just run "make nss.build" and not "make nss.clean && make nss.build" since the

Re: Fail to build on Windows 7 (32 bits)

On 18.08.2015 20:37, julien2412 wrote: > $ find workdir/UnpackedTarball/nss -name nspr4.lib > workdir/UnpackedTarball/nss/nspr/out/pr/src/nspr4.lib > build.log so the relevant difference is that your nsinstall.py command has "libnsp

Re: Fail to build on Windows 7 (32 bits)

Here it is! (see attachment) build.log Julien -- View this message in context: http://nabble.documentfoundation.org/Fail-to-build-on-Windows-7-32-bits-tp4156056p4157616.html Sent from the Dev mailing list archive at Nabble.com. _

Re: Fail to build on Windows 7 (32 bits)

On 18/08/2015 00:46, Ashod Nakashian wrote: 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 for

Re: Fail to build on Windows 7 (32 bits)

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

Re: Fail to build on Windows 7 (32 bits)

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

Re: Fail to build on Windows 7 (32 bits)

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? ___

Re: Fail to build on Windows 7 (32 bits)

I updated my local repo (still master sources), I still get the same. I searched in Opengrok for libnspr4.lib and found this: http://opengrok.libreoffice.org/xref/core/external/libxmlsec/xmlsec1-configure.patch#167 it seems the patch isn't applied since we've got this: 167 -XMLSEC_NSS_SOLIBS