-
Notifications
You must be signed in to change notification settings - Fork 262
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
Link error when compiling NCZhdf5filters.o on MinGW64 with netCDF 4.9.0 #2468
Comments
With the 4.6.0 Fortran release out the door, I am pivoting back to this and other issues we're seeing with the 4.9.0 release. I'll see if I can get this figured out and fixed, I want the release cycle for 4.9.1 to be a very short one. |
Would it be possible to enable plugins in the MinGW CI tests? And possibly also byte range support? |
I don't recall why they are disabled to begin with, so let's start by taking a look at what happens if we turn them on. |
@Alexander-Barth I'm curious, do you run into issues when trying to enable plugins or byterange? I am struggling to get things working, even just with the byterange, in a fresh MSYS2/MinGW64 environment. Starting with byterange, I've been able to eventually get things to compile using |
I have plugins building with Autotools here, but hadn't tried byterange. I'm waiting on test results to see what happens. (EDIT: enabling byterange and DAP on MinGW autotools build passes) I think the big thing with MinGW plugins is that |
I am still trying to update NetCDF for Julia users on Windows. In this test, I tried native compilation on Windows (using the MinGW64 toolchain from MSYS2).
NetCDF is configured as:
The MinGW64 compiler version is:
The full error message is:
These steps worked when compiling NetCDF 4.8.1 on the same machine.
It might be related to the LDFLAGS passed to make, which is also used here:
https://github.com/Unidata/netcdf-c/blob/main/.github/workflows/run_tests_win_mingw.yml#L49
Any help would be greatly appreciated!
Maybe this is related:
#2419
The text was updated successfully, but these errors were encountered: