You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have compiled the netcdf4 and hdf5 libraries statically (in my case, because I want to deploy to AWS Lambda), then the module is built but it cannot be loaded due to missing symbols:
Error: node_modules/netcdf4/build/Release/netcdf4.node: undefined symbol: H5T_NATIVE_SHORT_g
at Object.Module._extensions..node (internal/modules/cjs/loader.js:718:18)
at Module.load (internal/modules/cjs/loader.js:599:32)
It turns out this is due to a missing library dependency in binding.gyp, and the solution is to specify the dependent library:
I haven't been able to test this with shared libraries (as my environment is only building static ones) but if it doesn't break the shared library build, could this change be included for the benefit of those using static libraries?
The text was updated successfully, but these errors were encountered:
I don't think the change could be harmful, especially because hdf5 lib is already a dependency of netcdf, so this change does not add further pre-reqs.
Would you mind doing a PR?
If you have compiled the
netcdf4
andhdf5
libraries statically (in my case, because I want to deploy to AWS Lambda), then the module is built but it cannot be loaded due to missing symbols:It turns out this is due to a missing library dependency in
binding.gyp
, and the solution is to specify the dependent library:I haven't been able to test this with shared libraries (as my environment is only building static ones) but if it doesn't break the shared library build, could this change be included for the benefit of those using static libraries?
The text was updated successfully, but these errors were encountered: