Closed yantosca closed 1 year ago
Ah I see it. I had a typo in packages.yaml that caused the netCDF external package to point to the wrong path:
[holy7c12101 RockyLinux]$ spack -C ./spack-env/gnu12 uninstall --dependents netcdf-c /tyyqxxk
==> The following packages will be uninstalled:
-- linux-rocky8-x86_64 / gcc@12.2.0 -----------------------------
3uf3yiu cdo@2.1.0 tyyqxxk netcdf-c@4.9.2
==> Do you want to proceed? [y/N] y
==> Successfully uninstalled cdo@2.1.0%gcc@12.2.0~curl~external-grib1+fftw3+hdf5+libxml2~magics+netcdf+openmp~proj~szip+udunits2 build_system=autotools grib2=eccodes arch=linux-rocky8-x86_64/3uf3yiu
This might be a good warning for folks to check their packages.yaml
file! Thanks much!
I was able to build the NCO (netcdf operators) OK using gcc@10.2.0 but not with gcc@12.2.0. I am not sure if this is due to a cached prior setting my Spack environment:
Note that the path has a typo: (farc01 instead of fasrc01):
I think this was my own typo in my packages.yaml file. But I fixed it and then I regenerated the module files so I think this shouldn't be caching the error. I also did
spack clean -a
several times which should clean up the build.I have these modules loaded:
I am building from this folder
with this command
and my packages.yaml file is:
Thanks for any insights!