-
-
Notifications
You must be signed in to change notification settings - Fork 197
compiling app using v2.1.10 on Windows requires Admin privileges #866
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
I agree, this is annoying. I will take a look at it (since it being it my fault), however, it might take me some time to get to it. In the meantime, I think it should suffice for you to put the lines PackageCompiler.jl/src/PackageCompiler.jl Lines 1291 to 1298 in 846292c
inside an if !Sys.iswindows()
...
end block to guard against this behavior. Eventually, I think the right choice would be to do this library selection woopla for libstdc++ only on Linux systems, since this is the only OS for which this fancy libstdc++ loading is used in Julia. |
Also facing this issue. Thanks @sloede, also for the possible workaround. I'll give it a try! |
Hi |
I've implemented a potential solution in #869. It would be great if you could confirm that this PR fixes your issue. |
Hi, because of this issue, v2.1.10 is a breaking release under Windows causing issues with other libraries like in my case FMIExport.jl. Could this please be fixed by (a) revoking the release and release as breaking v2.2.0 or (b) deploying a fixing patch v2.1.11 in the near future? That would be great. Thanks in advance! |
Deal! |
This solves the issue for me on windows! |
v2.1.11 was just tagged, which should fix the Windows issues. It would be great if someone who reported the issue here could confirm that it is done. |
I can confirm that v2.1.11 solves this issue on my machine (Win10, Julia 1.9.3)! |
Thanks! |
This issue is split from #864. I failed to compile a mini app using v2.1.10 on Windows, which reports requiring Admin privileges. Running as admin can solve it. However, the privileges are not always available, and thus it would be great to remove the requirement.
versioninfo
error log
The text was updated successfully, but these errors were encountered: