Skip to content
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

Fails to build against libnetcdf built without netcdf4 support. #200

Closed
WardF opened this issue Sep 9, 2019 · 3 comments · Fixed by #201
Closed

Fails to build against libnetcdf built without netcdf4 support. #200

WardF opened this issue Sep 9, 2019 · 3 comments · Fixed by #201
Assignees

Comments

@WardF
Copy link
Member

WardF commented Sep 9, 2019

Will update with details, getting issue opened at moment. Fails to link against libnetcdf built without netCDF4 support. Needs to have configuration-time function checks and fenceposts added.

@WardF WardF self-assigned this Sep 9, 2019
@edhartnett
Copy link
Contributor

Well crap, I'm not testing this but I guess I better. ;-)

Is this the cmake or autotools build? Or both?

@WardF
Copy link
Member Author

WardF commented Sep 16, 2019

It's both, the tests are failing due to undefined references to:

  • nc_get_chunk_cache_ints
  • nc_get_var_chunk_cache_ints
  • nc_inq_var_chunking_ints
  • nc_set_var_chunk_cache_ints
  • nc_def_var_chunking_ints
  • nc_set_chunk_cache_ints

Still trying to nail down where/why this is happening; I'll also get to the C PR ASAP, but need to get a 4.7.2 release out to fix this; there are a number of packages which apparently instruct their users to compile netCDF_C without netCDF4 support, and we're fielding a lot of support requests due to this issue.

@WardF
Copy link
Member Author

WardF commented Sep 17, 2019

configure.ac was using nc_def_opaque to determine if libnetcdf.so was built with netCDF-4 support. This is now true even if netCDF-4 support isn't actually active. As a result, USE_NETCDF4 was flagged as TRUE even when it should haven't been. Doing some digging now and will follow up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants