-
-
Notifications
You must be signed in to change notification settings - Fork 268
lld-link: error: failed to write the output file: permission denied #3675
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Use |
Sorry about duplication issue commit. the -v dumps: binary E:\ldc2-1.25.0-windows-multilib\bin\ldc2.exe |
So you're trying to create a dlg.exe in the current working dir (which I can't find in your post, but oh well). What do you mean by Anyway, this is almost guaranteed not to have anything to do with LDC itself. It's the integrated LLD linker that fails to write the final .exe file; that has been bumped from v11.0.0 (LDC v1.24) to v11.0.1 with the new release, so you might have run into some LLD regression. |
Excuse me, I'd like to revise my description of the issue. On a real NTFS disk E:, the generated file is dlg.obj. But, in v1.24.0, everything is OK. this is dlg.d: import core.sys.windows.windows; enum { IDD_DIALOG1 = 100, } extern (Windows) nothrow @System extern (Windows) |
Even the simplest helloword program has the same result. import std.stdio; |
I can replicate the build failure in Wine 6.4 on Arch Linux, albeit with the different error message "path is invalid", see build log below. Thus, the The Hello World source:
I have installed LDC2 1.25.1 via extraction from the multilib archive. I build the Hello World with:
binary C:\ldc\bin\ldc2.exe Full build log of |
When compiling a (simple) D program, LDC 1.25.0 show:
lld-link: error: failed to write the output file: permission denied
And no executable generated but xxx.exe.xxxxxxx. In 1.24.0, no such error.
The OS is Win7 x64, FS is NTFS.
The text was updated successfully, but these errors were encountered: