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
> ls -l envs/unified-env/install/apple-clang/13.1.6/netcdf-cxx4-4.3.1-ul7tkg3/lib/
total 800
drwxr-sr-x 3 heinzell CIT\Domain Users 96 May 10 10:00 cmake
-rw-r--r-- 1 heinzell CIT\Domain Users 901 May 10 10:00 libnetcdf-cxx.settings
-rwxr-xr-x 1 heinzell CIT\Domain Users 402339 May 10 10:00 libnetcdf-cxx4.1.1.0.dylib
lrwxr-xr-x 1 heinzell CIT\Domain Users 26 May 10 10:00 libnetcdf-cxx4.1.dylib -> libnetcdf-cxx4.1.1.0.dylib
lrwxr-xr-x 1 heinzell CIT\Domain Users 22 May 10 10:00 libnetcdf-cxx4.dylib -> libnetcdf-cxx4.1.dylib
Error message
This creates errors for downstream packages such as met that look for the netcdf-cxx4 libraries with the old names. Having different library names for different build systems but for the same version of a package is not a good idea.
I proposed the move to cmake in #42766 because the mixing of autotools and cmake causes problems where cmake would use a system cmake netcdf-c instead of the autotools netcdf-c or vice versa. I had not noticed the discrepancy in library names, but I also don't use hard-coded library names (which, imo, should always be avoided).
I see this is already flagged upstream in Unidata/netcdf-cxx4#113 as of a few years ago. Curious to see what @WardF thinks. But this and pkgconfig compatibility might be good reason to have the complexity of maintaining both buildsystem code paths
Steps to reproduce the issue
Old autotools build:
Same version (!!!), new cmake build:
Error message
This creates errors for downstream packages such as
met
that look for the netcdf-cxx4 libraries with the old names. Having different library names for different build systems but for the same version of a package is not a good idea.Information on your system
Additional information
n/a
@WardF mentioning you as a maintainer of netcdf-cxx4
General information
spack debug report
and reported the version of Spack/Python/Platformspack maintainers <name-of-the-package>
and @mentioned any maintainersThe text was updated successfully, but these errors were encountered: