Re: Build Problem with Lode

2016-12-14 Thread Yossi Zahn


On 14/12/2016 10:50 AM, Noel Grandin wrote:
Some googling around suggests that this has something to do with 
Internet Exploder security zones, but who knows exactly what. The 
"fixes" are not great either, suggesting turning off various protections.
AFAIK, Internet Explorer security zones will only affect creation of 
activex objects within an Internet Explorer hosted script - not when 
using the standalone script host.


yossi
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Build Problem with Lode

2016-12-14 Thread Kaganski Mike
On 12/14/2016 11:29 AM, Jason Marshall wrote:
On 13/12/2016 08:00, Yossi Zahn wrote:
AFAIK the windows scripting host does not require .net framework at all.
Do you get the same error when creating a text file containing the following 
single line:
var fso = new ActiveXObject("Scripting.FileSystemObject");
and running it as such:
cscript /e:javascript path/to/file

I have created a text file test script in compliance with your instructions and 
called 'cscript' by directly defining the script engine using the 
'/e:javascript' parameter.  The call and output are as follows, but it seems 
that despite using the parameter, the same error arises as with the build:

Jason and Emma@JasonandEmma-PC ~
$ cscript /e:javascript scripttest.txt
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

C:\cygwin\home\Jason and Emma\scripttest.txt(1, 1) Microsoft JScript runtime 
error: Automation server can't create object

I guess that this would imply an issue with my individual set-up, as it seems 
that the use of the parameter that you and Thorsten have identified would work 
in the majority of cases.

Would anybody know what may have prevented this from working?

http://stackoverflow.com/questions/25922368/activexobject-creation-error-automation-server-cant-create-object-on-windows

Note the comments for the question on the link. I have checked, and at least my 
registry has this:

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{0D43FE01-F093-11CF-8940-00A0C9054228}\InprocServer32]
@="C:\\Windows\\SysWOW64\\scrrun.dll"
"ThreadingModel"="Both"

Checked with both 32-bit and 64-bit regedit (to make sure that path 
substitution doesn't change values).

--
Best regards,
Mike Kaganski
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Build Problem with Lode

2016-12-14 Thread Noel Grandin



On 2016/12/14 10:29 AM, Jason Marshall wrote:


I have created a text file test script in compliance with your instructions and 
called 'cscript' by directly defining
the script engine using the '/e:javascript' parameter.  The call and output are 
as follows, but it seems that despite
using the parameter, the same error arises as with the build:

Jason and Emma@JasonandEmma-PC ~
$ cscript /e:javascript scripttest.txt
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

C:\cygwin\home\Jason and Emma\scripttest.txt(1, 1) Microsoft JScript runtime 
error: Automation server can't create object

I guess that this would imply an issue with my individual set-up, as it seems 
that the use of the parameter that you and
Thorsten have identified would work in the majority of cases.

Would anybody know what may have prevented this from working?



Some googling around suggests that this has something to do with Internet Exploder security zones, but who knows exactly 
what. The "fixes" are not great either, suggesting turning off various protections.


Honestly, unless you really __want__ to do windows specific development on LibreOffice, I would suggest running Linux 
inside a VirtualBox VM on your Windows machine (or on another machine) and doing LibreOffice development there, where we 
are more likely to be able to help you get a working setup.


Sorry about this, Windows is just not a very robust development platform 
(despite having lots of nice tools available).
It's just way too easy to end up with a broken build environment for 
reasons completely outside our control.

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Build Problem with Lode

2016-12-14 Thread Yossi Zahn

On 14/12/2016 10:29 AM, Jason Marshall wrote:


I have created a text file test script in compliance with your
instructions and called 'cscript' by directly defining the script
engine using the '/e:javascript' parameter.  The call and output are
as follows, but it seems that despite using the parameter, the same
error arises as with the build:

Jason and Emma@JasonandEmma-PC ~
$ cscript /e:javascript scripttest.txt
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

C:\cygwin\home\Jason and Emma\scripttest.txt(1, 1) Microsoft JScript
runtime error: Automation server can't create object

I guess that this would imply an issue with my individual set-up, as
it seems that the use of the parameter that you and Thorsten have
identified would work in the majority of cases.

Would anybody know what may have prevented this from working?



You seem to be running cscript from the cygwin bash shell. Does the same
problem occur when running it from
a) the windows cmd shell (c:\windows\system32\cmd.exe)
b) a 32bit cmd prompt (c:\windows\syswow64\cmd.exe)

yossi

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Build Problem with Lode

2016-12-14 Thread Jason Marshall
Hi Yossi

On 13/12/2016 08:00, Yossi Zahn wrote:


On 11/12/2016 11:30 PM, Jason Marshall wrote:
I have tried to get some understanding of JScript and have inferred that for 
the purpose of building LibreOffice that it would require 'JScript .NET' as 
opposed to simply 'JScript', where the latter is for hosting JScript inside a 
webpage.  I have therefore checked the installation status of '.NET Framework' 
and can report that the following items are installed:
AFAIK the windows scripting host does not require .net framework at all.
Do you get the same error when creating a text file containing the following 
single line:
var fso = new ActiveXObject("Scripting.FileSystemObject");
and running it as such:
cscript /e:javascript path/to/file

I have created a text file test script in compliance with your instructions and 
called 'cscript' by directly defining the script engine using the 
'/e:javascript' parameter.  The call and output are as follows, but it seems 
that despite using the parameter, the same error arises as with the build:

Jason and Emma@JasonandEmma-PC ~
$ cscript /e:javascript scripttest.txt
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

C:\cygwin\home\Jason and Emma\scripttest.txt(1, 1) Microsoft JScript runtime 
error: Automation server can't create object

I guess that this would imply an issue with my individual set-up, as it seems 
that the use of the parameter that you and Thorsten have identified would work 
in the majority of cases.

Would anybody know what may have prevented this from working?

Thank you.

Jason
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Build Problem with Lode

2016-12-12 Thread Yossi Zahn



On 11/12/2016 11:30 PM, Jason Marshall wrote:
I have tried to get some understanding of JScript and have inferred 
that for the purpose of building LibreOffice that it would require 
'JScript .NET' as opposed to simply 'JScript', where the latter is for 
hosting JScript inside a webpage.  I have therefore checked the 
installation status of '.NET Framework' and can report that the 
following items are installed:

AFAIK the windows scripting host does not require .net framework at all.
Do you get the same error when creating a text file containing the 
following single line:

var fso = new ActiveXObject("Scripting.FileSystemObject");
and running it as such:
cscript /e:javascript path/to/file
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Build Problem with Lode

2016-12-12 Thread Thorsten Behrens
Jason Marshall wrote:
> > C:\cygwin\lode\dev\core\workdir\UnpackedTarball\xml2\win32\configure.js(181,
> >  2) Microsoft JScript > runtime error: Automation server can't create object
> 
Perhaps
https://cgit.freedesktop.org/libreoffice/core/commit/?id=7d69efd06dd1a1fee28c117e5ab79e557056f82c
needs some more tweaking?

Cheers,

-- Thorsten


signature.asc
Description: Digital signature
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Build Problem with Lode

2016-12-11 Thread Jason Marshall
Hi Noel

Noel Grandin wrote:

> Jason what kind of Windows is this? Because it seems like some part of the 
> Windows jscript runtime is not properly installed. Did you remove any Windows 
> components perhaps?

My Windows set-up is described as follows:

  *   Windows 7 Home Premium
  *   Service Pack 1
  *   32-bit

I can also confirm that the 'Programs and Features' part of Control Panel 
identifies that 'Microsoft Visual Studio Community 2013 with Update 5' is 
installed.

I have tried to get some understanding of JScript and have inferred that for 
the purpose of building LibreOffice that it would require 'JScript .NET' as 
opposed to simply 'JScript', where the latter is for hosting JScript inside a 
webpage.  I have therefore checked the installation status of '.NET Framework' 
and can report that the following items are installed:

  *   Microsoft .NET Framework 4.5 Multi-Targeting Pack
  *   Microsoft .NET Framework 4.5 SDK
  *   Microsoft .NET Framework 4.5.1 Multi-Targeting Pack
  *   Microsoft .NET Framework 4.5.1 Multi-Targeting Pack (ENU)
  *   Microsoft .NET Framework 4.5.1 SDK
  *   Microsoft .NET Framework 4.6.1

I have also checked in the 'Services' section of the 'Administrative Tools' 
section of Control Panel and have identified that the following entries are 
apparent with the associated 'Status' and 'Startup Type':

  *   Microsoft .NET Framework NGEN v2.0.50727_X86
 *   Status: null
 *   Startup Type: Disabled
  *   Microsoft .NET Framework NGEN v4.0.30319_X86
 *   Status: null
 *   Startup Type: Automatic (Delayed Start)

Assuming there is nothing untoward about the JScript set-up as described above 
and that I am not 'barking up the wrong tree' in making reference to the .NET 
Framework, is there any way to more generally confirm that my JScript set-up in 
Windows is okay?

Thanks

Jason
On 11/12/2016 17:42, Noel Grandin wrote:
Jason what kind of Windows is this? Because it seems like some part of the 
Windows jscript runtime is not properly installed. Did you remove any Windows 
components perhaps?
On Sun, 11 Dec 2016 at 19:39, Oliver Brinzing 
> wrote:

Hi Jason,

 >> C:\cygwin\lode\dev\core\workdir\UnpackedTarball\xml2\win32\configure.js(181,
 >>  2) Microsoft
JScript > runtime error: Automation server can't create object

i cannot confirm your build problems, but building current master with a fresh 
lode setup (win 10
64bit, vs2013) fails for me too.



Regards
Oliver


[SLC] sw
warn:sal.rtl:9680:14236:sal/rtl/bootstrap.cxx:379: couldn't open file:
file:///D:/lo_sources/lode/dev/core/workdir/LinkTarget/Executable/cppunittester.ini
warn:vcl.pdfwriter:9680:14236:vcl/source/gdi/pdfwriter_impl.cxx:6844:
CryptAcquireCertificatePrivateKey failed: Das Zertifikat und der private 
Schlüssel für die
Entschlüsselung wurden nicht gefunden.
warn:xmlsecurity.pdfio:9680:14236:xmlsecurity/source/pdfio/pdfdocument.cxx:965: 
PDFDocument::Sign:
PDFWriter::Sign() failed
D:/lo_sources/lode/dev/core/xmlsecurity/qa/unit/pdfsigning/pdfsigning.cxx:172:PDFSigningTest::testPDFAdd
assertion failed
- Expression: aDocument.Sign(aCertificates[0], "test", true)

PDFSigningTest::testPDFAdd finished in: 172ms
warn:vcl.pdfwriter:9680:14236:vcl/source/gdi/pdfwriter_impl.cxx:6844:
CryptAcquireCertificatePrivateKey failed: Das Zertifikat und der private 
Schlüssel für die
Entschlüsselung wurden nicht gefunden.
warn:xmlsecurity.pdfio:9680:14236:xmlsecurity/source/pdfio/pdfdocument.cxx:965: 
PDFDocument::Sign:
PDFWriter::Sign() failed
D:/lo_sources/lode/dev/core/xmlsecurity/qa/unit/pdfsigning/pdfsigning.cxx:172:PDFSigningTest::testPDFAdd2
assertion failed
- Expression: aDocument.Sign(aCertificates[0], "test", true)

PDFSigningTest::testPDFAdd2 finished in: 23ms
PDFSigningTest::testPDFRemove finished in: 28ms
PDFSigningTest::testPDFRemoveAll finished in: 48ms
PDFSigningTest::testPDF14Adobe finished in: 27ms
PDFSigningTest::testPDF16Adobe finished in: 18ms
func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.

func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.

func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.

func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.

func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.


Re: Build Problem with Lode

2016-12-11 Thread Noel Grandin
Jason what kind of Windows is this? Because it seems like some part of the
Windows jscript runtime is not properly installed. Did you remove any
Windows components perhaps?
On Sun, 11 Dec 2016 at 19:39, Oliver Brinzing 
wrote:

>
> Hi Jason,
>
>  >>
> C:\cygwin\lode\dev\core\workdir\UnpackedTarball\xml2\win32\configure.js(181,
> 2) Microsoft
> JScript > runtime error: Automation server can't create object
>
> i cannot confirm your build problems, but building current master with a
> fresh lode setup (win 10
> 64bit, vs2013) fails for me too.
>
>
>
> Regards
> Oliver
>
>
> [SLC] sw
> warn:sal.rtl:9680:14236:sal/rtl/bootstrap.cxx:379: couldn't open file:
>
> file:///D:/lo_sources/lode/dev/core/workdir/LinkTarget/Executable/cppunittester.ini
> warn:vcl.pdfwriter:9680:14236:vcl/source/gdi/pdfwriter_impl.cxx:6844:
> CryptAcquireCertificatePrivateKey failed: Das Zertifikat und der private
> Schlüssel für die
> Entschlüsselung wurden nicht gefunden.
> warn:xmlsecurity.pdfio:9680:14236:xmlsecurity/source/pdfio/pdfdocument.cxx:965:
> PDFDocument::Sign:
> PDFWriter::Sign() failed
>
> D:/lo_sources/lode/dev/core/xmlsecurity/qa/unit/pdfsigning/pdfsigning.cxx:172:PDFSigningTest::testPDFAdd
> assertion failed
> - Expression: aDocument.Sign(aCertificates[0], "test", true)
>
> PDFSigningTest::testPDFAdd finished in: 172ms
> warn:vcl.pdfwriter:9680:14236:vcl/source/gdi/pdfwriter_impl.cxx:6844:
> CryptAcquireCertificatePrivateKey failed: Das Zertifikat und der private
> Schlüssel für die
> Entschlüsselung wurden nicht gefunden.
> warn:xmlsecurity.pdfio:9680:14236:xmlsecurity/source/pdfio/pdfdocument.cxx:965:
> PDFDocument::Sign:
> PDFWriter::Sign() failed
>
> D:/lo_sources/lode/dev/core/xmlsecurity/qa/unit/pdfsigning/pdfsigning.cxx:172:PDFSigningTest::testPDFAdd2
> assertion failed
> - Expression: aDocument.Sign(aCertificates[0], "test", true)
>
> PDFSigningTest::testPDFAdd2 finished in: 23ms
> PDFSigningTest::testPDFRemove finished in: 28ms
> PDFSigningTest::testPDFRemoveAll finished in: 48ms
> PDFSigningTest::testPDF14Adobe finished in: 27ms
> PDFSigningTest::testPDF16Adobe finished in: 18ms
>
> func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
> ;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich
> beendet.
>
>
> func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
> ;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich
> beendet.
>
>
> func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
> ;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich
> beendet.
>
>
> func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
> ;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich
> beendet.
>
>
> func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
> ;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich
> beendet.
>
>
> func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
> ;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich
> beendet.
>
>
> func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
> ;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich
> beendet.
>
>
> func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion:
> ;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich
> beendet.
>
> warn:vcl.pdfwriter:9680:14236:vcl/source/gdi/pdfwriter_impl.cxx:6844:
> CryptAcquireCertificatePrivateKey failed: Das Zertifikat und der private
> Schlüssel für die
> Entschlüsselung wurden nicht gefunden.
> warn:xmlsecurity.pdfio:9680:14236:xmlsecurity/source/pdfio/pdfdocument.cxx:965:
> PDFDocument::Sign:
> PDFWriter::Sign() failed
>
> D:/lo_sources/lode/dev/core/xmlsecurity/qa/unit/pdfsigning/pdfsigning.cxx:172:PDFSigningTest::testPDF16Add
> assertion failed
> - Expression: aDocument.Sign(aCertificates[0], "test", true)
>
> PDFSigningTest::testPDF16Add finished in: 28ms
> PDFSigningTest::testPDF14LOWin finished in: 14ms
> PDFSigningTest::testPDFPAdESGood finished in: 12ms
> PDFSigningTest::testPartial finished in: 10ms
> warn:vcl.pdfwriter:9680:14236:vcl/source/gdi/pdfwriter_impl.cxx:6844:
> CryptAcquireCertificatePrivateKey failed: Das Zertifikat und der private
> Schlüssel für die
> Entschlüsselung wurden nicht gefunden.
> warn:xmlsecurity.pdfio:9680:14236:xmlsecurity/source/pdfio/pdfdocument.cxx:965:
> PDFDocument::Sign:
> PDFWriter::Sign() failed
>
> 

Re: Build Problem with Lode

2016-12-11 Thread Oliver Brinzing


Hi Jason,

>> C:\cygwin\lode\dev\core\workdir\UnpackedTarball\xml2\win32\configure.js(181, 2) Microsoft 
JScript > runtime error: Automation server can't create object


i cannot confirm your build problems, but building current master with a fresh lode setup (win 10 
64bit, vs2013) fails for me too.




Regards
Oliver


[SLC] sw
warn:sal.rtl:9680:14236:sal/rtl/bootstrap.cxx:379: couldn't open file: 
file:///D:/lo_sources/lode/dev/core/workdir/LinkTarget/Executable/cppunittester.ini
warn:vcl.pdfwriter:9680:14236:vcl/source/gdi/pdfwriter_impl.cxx:6844: 
CryptAcquireCertificatePrivateKey failed: Das Zertifikat und der private Schlüssel für die 
Entschlüsselung wurden nicht gefunden.
warn:xmlsecurity.pdfio:9680:14236:xmlsecurity/source/pdfio/pdfdocument.cxx:965: PDFDocument::Sign: 
PDFWriter::Sign() failed

D:/lo_sources/lode/dev/core/xmlsecurity/qa/unit/pdfsigning/pdfsigning.cxx:172:PDFSigningTest::testPDFAdd
assertion failed
- Expression: aDocument.Sign(aCertificates[0], "test", true)

PDFSigningTest::testPDFAdd finished in: 172ms
warn:vcl.pdfwriter:9680:14236:vcl/source/gdi/pdfwriter_impl.cxx:6844: 
CryptAcquireCertificatePrivateKey failed: Das Zertifikat und der private Schlüssel für die 
Entschlüsselung wurden nicht gefunden.
warn:xmlsecurity.pdfio:9680:14236:xmlsecurity/source/pdfio/pdfdocument.cxx:965: PDFDocument::Sign: 
PDFWriter::Sign() failed

D:/lo_sources/lode/dev/core/xmlsecurity/qa/unit/pdfsigning/pdfsigning.cxx:172:PDFSigningTest::testPDFAdd2
assertion failed
- Expression: aDocument.Sign(aCertificates[0], "test", true)

PDFSigningTest::testPDFAdd2 finished in: 23ms
PDFSigningTest::testPDFRemove finished in: 28ms
PDFSigningTest::testPDFRemoveAll finished in: 48ms
PDFSigningTest::testPDF14Adobe finished in: 27ms
PDFSigningTest::testPDF16Adobe finished in: 18ms
func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion: 
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.


func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion: 
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.


func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion: 
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.


func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion: 
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.


func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion: 
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.


func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion: 
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.


func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion: 
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.


func=xmlSecPtrListFinalize:file=..\src\list.c:line=130:obj=unknown:subj=xmlSecPtrListIsValid(list):error=100:assertion: 
;last error=0 (0x);last error msg=Der Vorgang wurde erfolgreich beendet.


warn:vcl.pdfwriter:9680:14236:vcl/source/gdi/pdfwriter_impl.cxx:6844: 
CryptAcquireCertificatePrivateKey failed: Das Zertifikat und der private Schlüssel für die 
Entschlüsselung wurden nicht gefunden.
warn:xmlsecurity.pdfio:9680:14236:xmlsecurity/source/pdfio/pdfdocument.cxx:965: PDFDocument::Sign: 
PDFWriter::Sign() failed

D:/lo_sources/lode/dev/core/xmlsecurity/qa/unit/pdfsigning/pdfsigning.cxx:172:PDFSigningTest::testPDF16Add
assertion failed
- Expression: aDocument.Sign(aCertificates[0], "test", true)

PDFSigningTest::testPDF16Add finished in: 28ms
PDFSigningTest::testPDF14LOWin finished in: 14ms
PDFSigningTest::testPDFPAdESGood finished in: 12ms
PDFSigningTest::testPartial finished in: 10ms
warn:vcl.pdfwriter:9680:14236:vcl/source/gdi/pdfwriter_impl.cxx:6844: 
CryptAcquireCertificatePrivateKey failed: Das Zertifikat und der private Schlüssel für die 
Entschlüsselung wurden nicht gefunden.
warn:xmlsecurity.pdfio:9680:14236:xmlsecurity/source/pdfio/pdfdocument.cxx:965: PDFDocument::Sign: 
PDFWriter::Sign() failed

D:/lo_sources/lode/dev/core/xmlsecurity/qa/unit/pdfsigning/pdfsigning.cxx:172:PDFSigningTest::testSigningCertificateAttribute
assertion failed
- Expression: aDocument.Sign(aCertificates[0], "test", true)

PDFSigningTest::testSigningCertificateAttribute finished in: 20ms
PDFSigningTest::testGood finished in: 52ms
PDFSigningTest::testTokenize finished in: 44ms
warn:xmlsecurity.pdfio:9680:14236:xmlsecurity/source/pdfio/pdfdocument.cxx:2237: 
PDFDocument::ValidateSignature: unsupported sub-filter: 'ETSI.RFC3161'

Re: Build Problem with Lode

2016-12-11 Thread Jason Marshall
Jason Marshall <j_k_marshall_2...@live.com> wrote:

[snip]

> I am attempting to build LibreOffice on a Windows 7 32-but platform.

[snip]

> However, at a relatively advanced stage of the build, I receive the following 
> error message and the build terminates:

{snip]

> [build UNO] cppuhelper
> Microsoft (R) Windows Script Host Version 5.8
> Copyright (C) Microsoft Corporation. All rights reserved.

> C:\cygwin\lode\dev\core\workdir\UnpackedTarball\xml2\win32\configure.js(181, 
> 2) Microsoft JScript > runtime error: Automation server can't create object

> Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
> Copyright (C) Microsoft Corporation.  All rights reserved.

> NMAKE : fatal error U1064: MAKEFILE not found and no target specified
> Stop.
> make[1]: *** 
> [C:/cygwin/lode/dev/core/external/libxml2/ExternalProject_xml2.mk:34: > 
> C:/cygwin/lode/dev/core/workdir/ExternalProject/xml2/build] Error 1
> make[1]: *** Waiting for unfinished jobs
> make: *** [Makefile:266: build] Error 2


Noel Grandin <noelgran...@gmail.com> wrote:


>> That smells to me like an over enthusiastic anti virus program


I have completely disabled the F-Secure anti-virus program and also ensured 
that Windows Defender is switched off, meaning that no ant-virus systems are 
active during the build.  However, I still receive the following error messages 
as the build terminates on two consecutive attempts:


Jason and Emma@JasonandEmma-PC /lode/dev/core
$ ../../opt/bin/make 2>&1 | tee build.log
C:/cygwin/lode/opt/bin/make -j 2  -rs -f 
C:/cygwin/lode/dev/core/Makefile.gbuildall
[build DEP] LNK:Library/shlxthdl_x64.dll
[build DEP] LNK:Library/shlxthdl.dll
[build HPP] udkapi
[build UNO] offapi
[build DBc] offapi
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

C:\cygwin\lode\dev\core\workdir\UnpackedTarball\xml2\win32\configure.js(181, 2) 
Microsoft JScript runtime error: Automation server can't create object

Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
Copyright (C) Microsoft Corporation.  All rights reserved.

NMAKE : fatal error U1064: MAKEFILE not found and no target specified
Stop.
make[1]: *** 
[C:/cygwin/lode/dev/core/external/libxml2/ExternalProject_xml2.mk:34: 
C:/cygwin/lode/dev/core/workdir/ExternalProject/xml2/build] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [Makefile:266: build] Error 2


Jason and Emma@JasonandEmma-PC /lode/dev/core
$ ../../opt/bin/make 2>&1 | tee build.log
C:/cygwin/lode/opt/bin/make -j 2  -rs -f 
C:/cygwin/lode/dev/core/Makefile.gbuildall
[build HPP] offapi
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

C:\cygwin\lode\dev\core\workdir\UnpackedTarball\xml2\win32\configure.js(181, 2) 
Microsoft JScript runtime error: Automation server can't create object

Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
Copyright (C) Microsoft Corporation.  All rights reserved.

NMAKE : fatal error U1064: MAKEFILE not found and no target specified
Stop.
make[1]: *** 
[C:/cygwin/lode/dev/core/external/libxml2/ExternalProject_xml2.mk:34: 
C:/cygwin/lode/dev/core/workdir/ExternalProject/xml2/build] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [Makefile:266: build] Error 2


This is the same message as is received when F-Secure was not disabled.  
However, perhaps interestingly the failure seems to be associated or else 
coincide with different build tasks (i. e. '[build DBc] offapi' on first build 
and then '[build HPP] offapi' on second build).


Having consulted the 'build.log' file, the contents are essentially as above on 
the second build attempt, but the file identifies that the build process is 
called with the following parameters:


C:/cygwin/lode/opt/bin/make -j 2  -rs -f 
C:/cygwin/lode/dev/core/Makefile.gbuild   all


Any further ideas would be much appreciated.


Thanks


Jason




From: Noel Grandin <noelgran...@gmail.com>
Sent: 04 December 2016 15:50
To: Jason Marshall; libreoffice@lists.freedesktop.org
Subject: Re: Build Problem with Lode

That smells to me like an over enthusiastic anti virus program
On Sun, 04 Dec 2016 at 15:17, Jason Marshall 
<j_k_marshall_2...@live.com<mailto:j_k_marshall_2...@live.com>> wrote:

Dear Sir/ Madam


I am attempting to build LibreOffice on a Windows 7 32-but platform.  Initially 
I attempted to do this without recourse to lode but the build failed.  I was 
advised to re-attempt a build but using the Lode project.  I have been able to 
successfully get Lode to setup a dev build environment, with the following 
command completing successfully:


./setup --dev


Following that, I then run the following:


cd dev/core
./autogen.sh
../../opt/bin/make 2>&1 | tee build.log


However, at a relatively advanced stage of

Re: Build Problem with Lode

2016-12-06 Thread Norbert Thiebaud
On Mon, Dec 5, 2016 at 1:48 PM, Jason Marshall
 wrote:
> Thank you for this information and advice.

While on the topic of information and advice, please read

http://mailformat.dan.info/quoting/bottom-posting.html

Norbert

---
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


RE: Build Problem with Lode

2016-12-05 Thread Jason Marshall
Thank you for this information and advice.

From: slacka<mailto:lukebe...@hotmail.com>
Sent: ‎04/‎12/‎2016 23:45
To: libreoffice@lists.freedesktop.org<mailto:libreoffice@lists.freedesktop.org>
Subject: RE: Build Problem with Lode

Jason Marshall wrote
> From your experience, is it best to disable anti-virus entirely during the
> build, or should it be configured to ignore certain programs associated
> with the build?

As you can see from the build notes
<https://wiki.documentfoundation.org/Development/BuildingOnWindows#Norton_Antivirus_breaking_the_build>
ever different anti-virus programs have different false positives. If you
want to take the time to review the log and manually whitelist each
quarantined file, you can keep your anti-virus software enabled. Disabling
it is the universal solution with the added bonus of speeding up build
times.



Jason Marshall wrote
> Would the build still proceed if I disconnected my internet connection? I
> ask because if I need to disable anti-virus, I would prefer to also
> disable my internet connection for that period.

I've lost Internet in the middle of builds and still had them succeed.

I've browsed the Internet for years without AV software, and never once been
infected by malware. Then again, my main user account has lacked admin
privileges since my win2K days. I'm fanatical about keeping my OS/Browser
fully updated and have had flash set to only click-to-play and use the
NoScript extension to only allow JS from whitelisted sites since those
options have existed.

No AV software is 100% effective. They do not cover every virus signature
and cannot detect all new threats. I worked in IT for a large corporation.
During that time we were hit several times by 0-day infections that got to
our users before their signature had made it into our vendor’s DB. So if
you're browsing sketchy sites with outdated software and relying 100% on
your AV software to protect you, you're asking for trouble.



--
View this message in context: 
http://nabble.documentfoundation.org/Build-Problem-with-Lode-tp4201726p4201761.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Build Problem with Lode

2016-12-04 Thread Noel Grandin

mostly I just mark the entire libreoffice build + source folder as being 
excluded from AV.

Yes, you can disable your internet connection after the download phase is 
complete, and the build will still work.

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


RE: Build Problem with Lode

2016-12-04 Thread slacka
Jason Marshall wrote
> From your experience, is it best to disable anti-virus entirely during the
> build, or should it be configured to ignore certain programs associated
> with the build?

As you can see from the build notes

  
ever different anti-virus programs have different false positives. If you
want to take the time to review the log and manually whitelist each
quarantined file, you can keep your anti-virus software enabled. Disabling
it is the universal solution with the added bonus of speeding up build
times.



Jason Marshall wrote
> Would the build still proceed if I disconnected my internet connection? I
> ask because if I need to disable anti-virus, I would prefer to also
> disable my internet connection for that period.

I've lost Internet in the middle of builds and still had them succeed.

I've browsed the Internet for years without AV software, and never once been
infected by malware. Then again, my main user account has lacked admin
privileges since my win2K days. I'm fanatical about keeping my OS/Browser
fully updated and have had flash set to only click-to-play and use the
NoScript extension to only allow JS from whitelisted sites since those
options have existed.

No AV software is 100% effective. They do not cover every virus signature
and cannot detect all new threats. I worked in IT for a large corporation.
During that time we were hit several times by 0-day infections that got to
our users before their signature had made it into our vendor’s DB. So if
you're browsing sketchy sites with outdated software and relying 100% on
your AV software to protect you, you're asking for trouble.



--
View this message in context: 
http://nabble.documentfoundation.org/Build-Problem-with-Lode-tp4201726p4201761.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


RE: Build Problem with Lode

2016-12-04 Thread Jason Marshall
Hi Noel

Thanks for your response. From your experience, is it best to disable 
anti-virus entirely during the build, or should it be configured to ignore 
certain programs associated with the build?

Also, I note that at the start of the build some further files are downloaded; 
however, based on these files having successfully downloaded on the first build 
attempt, would the build still proceed if I disconnected my internet 
connection? I ask because if I need to disable anti-virus, I would prefer to 
also disable my internet connection for that period.

Best regards

Jason

From: Noel Grandin<mailto:noelgran...@gmail.com>
Sent: ‎04/‎12/‎2016 15:50
To: Jason Marshall<mailto:j_k_marshall_2...@live.com>; 
libreoffice@lists.freedesktop.org<mailto:libreoffice@lists.freedesktop.org>
Subject: Re: Build Problem with Lode

That smells to me like an over enthusiastic anti virus program
On Sun, 04 Dec 2016 at 15:17, Jason Marshall 
<j_k_marshall_2...@live.com<mailto:j_k_marshall_2...@live.com>> wrote:

Dear Sir/ Madam


I am attempting to build LibreOffice on a Windows 7 32-but platform.  Initially 
I attempted to do this without recourse to lode but the build failed.  I was 
advised to re-attempt a build but using the Lode project.  I have been able to 
successfully get Lode to setup a dev build environment, with the following 
command completing successfully:


./setup --dev


Following that, I then run the following:


cd dev/core
./autogen.sh
../../opt/bin/make 2>&1 | tee build.log


However, at a relatively advanced stage of the build, I receive the following 
error message and the build terminates:


[build UNO] cppuhelper
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

C:\cygwin\lode\dev\core\workdir\UnpackedTarball\xml2\win32\configure.js(181, 2) 
Microsoft JScript runtime error: Automation server can't create object

Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
Copyright (C) Microsoft Corporation.  All rights reserved.

NMAKE : fatal error U1064: MAKEFILE not found and no target specified
Stop.
make[1]: *** 
[C:/cygwin/lode/dev/core/external/libxml2/ExternalProject_xml2.mk:34: 
C:/cygwin/lode/dev/core/workdir/ExternalProject/xml2/build] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [Makefile:266: build] Error 2


This message is precisely the same as that which was received when I attempted 
to build without Lode.  Accordingly, it would seem that the use of Lode has not 
solved the problem, with likely the problem lying elsewhere.

I note that the error message above makes reference to the following script:


C:\cygwin\lode\dev\core\workdir\UnpackedTarball\xml2\win32\configure.js(181, 2) 
Microsoft JScript runtime error: Automation server can't create object


I have viewed this script at the line identified in the error, which is pasted 
as follows:


fso = new ActiveXObject("Scripting.FileSystemObject");


I would infer that this is a JScript issue, but am not absolutely familiar with 
such scripting.  It looks like the command above is fairly simple, which 
perhaps indicates that the issues lies elsewhere.


Would anybody have any ideas as to what the problem may be?


Thank you for your time.


Yours faithfully


Jason Marshall

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org<mailto:LibreOffice@lists.freedesktop.org>
https://lists.freedesktop.org/mailman/listinfo/libreoffice
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: Build Problem with Lode

2016-12-04 Thread Noel Grandin
That smells to me like an over enthusiastic anti virus program
On Sun, 04 Dec 2016 at 15:17, Jason Marshall 
wrote:

> Dear Sir/ Madam
>
>
> I am attempting to build LibreOffice on a Windows 7 32-but platform.
> Initially I attempted to do this without recourse to lode but the build
> failed.  I was advised to re-attempt a build but using the Lode project.  I
> have been able to successfully get Lode to setup a dev build environment,
> with the following command completing successfully:
>
>
> ./setup --dev
>
>
> Following that, I then run the following:
>
>
> cd dev/core
> ./autogen.sh
> ../../opt/bin/make 2>&1 | tee build.log
>
>
> However, at a relatively advanced stage of the build, I receive the
> following error message and the build terminates:
>
>
> [build UNO] cppuhelper
> Microsoft (R) Windows Script Host Version 5.8
> Copyright (C) Microsoft Corporation. All rights reserved.
>
> C:\cygwin\lode\dev\core\workdir\UnpackedTarball\xml2\win32\configure.js(181,
> 2) Microsoft JScript runtime error: Automation server can't create object
>
>
> Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
> Copyright (C) Microsoft Corporation.  All rights reserved.
>
> NMAKE : fatal error U1064: MAKEFILE not found and no target specified
> Stop.
> make[1]: ***
> [C:/cygwin/lode/dev/core/external/libxml2/ExternalProject_xml2.mk:34:
> C:/cygwin/lode/dev/core/workdir/ExternalProject/xml2/build] Error 1
> make[1]: *** Waiting for unfinished jobs
> make: *** [Makefile:266: build] Error 2
>
>
> This message is precisely the same as that which was received when I
> attempted to build without Lode.  Accordingly, it would seem that the use
> of Lode has not solved the problem, with likely the problem lying elsewhere.
>
> I note that the error message above makes reference to the following
> script:
>
>
> C:\cygwin\lode\dev\core\workdir\UnpackedTarball\xml2\win32\configure.js(181,
> 2) Microsoft JScript runtime error: Automation server can't create object
>
>
> I have viewed this script at the line identified in the error, which is
> pasted as follows:
>
>
> fso = new ActiveXObject("Scripting.FileSystemObject");
>
>
> I would infer that this is a JScript issue, but am not absolutely familiar
> with such scripting.  It looks like the command above is fairly simple,
> which perhaps indicates that the issues lies elsewhere.
>
>
> Would anybody have any ideas as to what the problem may be?
>
>
> Thank you for your time.
>
>
> Yours faithfully
>
>
> Jason Marshall
>
> ___
> LibreOffice mailing list
> LibreOffice@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/libreoffice
>
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice