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


Hi.
for me, granting the user read/write access to the MachineKeys Folder was exactly the right 
solution for this error.
I’m building inside a VM, so I didn’t really care about windows warning messages.

There is another solution involving registry entries floating around that didn’t work for me.

Regards,
Julian

Von: LibreOffice [mailto:libreoffice-bounces@lists.freedesktop.org] Im Auftrag von anshu khare
Gesendet: Sonntag, 5. Juli 2020 18:07
An: libreoffice <libreoffice@lists.freedesktop.org>
Betreff: [EXTERN]-Error in building LibreOffice

Hi

When I run

 /opt/lo/bin/make gb_COLOR=1

it gives the following error

ALINK: error AL1078: Error signing assembly -- Access is denied.
make[1]: *** [C:/sources/libo-core/solenv/gbuild/CliAssembly.mk:82: 
C:/build/workdir/CliAssemblyTarget/cli_basetypes.done] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:282: build] Error 2

This link: https://github.com/dotnet/runtime/issues/15416

says that I have to add myself to the list of permissions of 
C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys folder with Full Control.

When I go this path I find that MachineKeys is a system file and editing it can cause harm to my pc.

Is it the correct solution or there is something else that needs to be focussed on?

If it is the correct solution, then which permissions do I have to edit the attached picture?



Warm regards
Anshu



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.