-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
[BUG] windows server 2022 - unable to load gdal_wrap #150
Comments
Could you please post a MRE if available. Also you can try to run LDD from GitBash. |
Thanks for info. I have recreated a Windows Server 2022 eval from scratch, to have the same version as you (cf screenshot). Then i have generated a MRE project as minimal as possible to reproduce the same behavior (it is ok on win 11 but not win 2022). for the LDD git bash, i can run it on the project .dll but when i try to use it on gdal.dll or gdal_wrap.dll, it keeps running for few hours without displaying any output. do you know if it is the normal behavior ? Since we use the exact same version of SRV2022 EVAL (without any modification), i think we can skip this issue. any idea ? :) |
This comment was marked as off-topic.
This comment was marked as off-topic.
@dawsidious I took me a while. I have installed VirtualBox and with the same configuration I have a repro. It's 100% missing AVX2, I have tested with disabled Hyper-V. I can't test it currently but recommend you to try disabling Hyper-V and this will enable AVX/AVX2 instructions in your VM. Edit: I had to disable Core Isolation > Memory Integrity to force turn off Hyper-V. |
Closing due to inactivity. |
Hello there :-)
I have an ASP.NET WEB API c# project using gdal which includes :
I tried both 3.9.1.246 and 3.9.1.247 (both failed).
I publish it through Visual studio with these parameters:
the project runs fine on :
output :
the project crashes on windows server 2022 (21H2 20348.2655 OR 20348.2461).
the file gdal_wrap.dll is already in the folder; do you have any idea on what i do wrong ? :)
Thanks a lot for your help !
The text was updated successfully, but these errors were encountered: