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


I found the files it is complaining about under /tmp/ooopackaing/...

The problem is that it is creating files with no permissions. e.g.
D:\Dev\cygwin\tmp\ooopackaging\i_106601351284799\wntmsci12.pro\LibreOffice_Dev\native\zip\en-US\00\basicsrvdepot_zip\CommonLang.xba
has no read/write/execute permissions set for anyone.

I opened a second Cygwin window and cd'd to /tmp. When the build got
to the part right before it executes makecab.exe in the first windows,
I had the second cygwin window execute:
chmod -R a=rwx ooopackaging

After that, the build process finished and said it was successful.

Is there some reason this would be happening for me? Other people seem
to be making Windows builds without this problem, right?

After the build ran, although there was an installer at:
instsetoo_native\wntmsci12.pro\LibreOffice_Dev\native\install\en-US\LibO-Dev_3.7.0.0.alpha0_Win_x86_install_en-US.msi
when I tried to install it, it failed with the following error:

Error 1935.An error occurred during the installation of assembly.
'cli_cppuhelper,publicKeyToken="ce2cb7e279207b93",version="1.0.22.0",culture="neutral",processorArchitecture="x86"'.
Please refer to Help and Support for more infor...

It looks like other people are getting that error too though, so maybe
this is as far as I can get until that is resolved...?
( https://bugs.freedesktop.org/show_bug.cgi?id=55290 )

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.