No permission to write output when building on win10

[Raymond Toy]

Haven't build chromium on windows in while, but I can't seem to build it locally anymore.  I get this error:

LINK(DLL) protobuf_lite.dll protobuf_lite.dll.lib protobuf_lite.dll.pdb
FAILED: protobuf_lite.dll protobuf_lite.dll.lib protobuf_lite.dll.pdb
ninja -t msvc -e environment.x64 -- ../../third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo /IMPLIB:./protobuf_lite.dll.lib /DLL /OUT:./protobuf_lite.dll /PDB:./protobuf_lite.dll.pdb @./protobuf_lite.dll.rsp
lld-link: error: failed to write the output file: permission denied

My gn config is pretty simple:

is_debug = false

is_component_build = true
use_goma = true
goma_dir = "c:\\src\\goma\\goma-win64"
proprietary_codecs = true
ffmpeg_branding = "Chrome"

What stupid thing am I doing? I used to be able to build on windows without problems.

[Peter Boström]

A shot in the dark, are you currently running chrome.exe? It needs to be closed so that DLLs and other files in use can be overwritten, *nixes work differently.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAE3TgXFchcice6W3jys2g41Vqt4LiBiUGPKu_MXwo03CpXf34w%40mail.gmail.com.

[Raymond Toy]

I was running chrome.exe (official beta build).  I did discover something is holding on to the out/Release directory so I can't even rename it. Don't know what, but a reboot took care of that.  Now I'm running into a problem with bit9 not allowing nasm to run.  I'll follow up internally about that problem.

Thanks for your suggestion!

[Bruce Dawson]

Next time somebody hits this problem on Windows I recommend using the sysinternals handle tool. You can usually use that to find out who has locks on a particular file or directory. I think that procexp can also be used. Having the entire sysinternals suite in your path is probably a good idea.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.