> Thanks for the email. As mentioned before, I have recompiled netcdf dozens > of time and follow the same procedure (make distclean, configure ..., > make, make check, and make install) but some information in nc-config is > not updated automatically and give me the same old paths. I always compile > netcdf and other libraries in my login, so, there are no issues of > permissions as well. I even compiled a different version of netcdf (4.0.1) > and when I ran nc-config, I got the same netCDF 4.1.3 against --version > and the same old directory paths for --flibs, --fflags, --cflags and > --libs. > > So it is definitely not a make install issue. It is something else. > Nc-config gives important information about netcdf configuration. If some > information is incorrect then I won't trust the rest. I will greatly > appreciate if you could look into this and suggest some solution. Does the date modified on the nc-config file change after you run "make install" to show the same date and time as when "make install" was run? You could determine this with ls -l `which nc-config` for example. Are you sure your PATH environment variable has the directory named in the --prefix option to configure before any other directory that contains an nc-config executable? You can determine this just by running "which nc-config" and comparing the result to where you expect the nc-config to have been installed. If the answer to both the questions above is "yes", please send the complete output from running "make install" as well as the outputs from running "ls -lt" on the bin and lib directories under the install directory. Thanks. --Russ > On 12/12/11 7:26 AM, "Unidata netCDF Support" > <address@hidden> wrote: > > >Hi Basit, > > > >> In the bin directory of netcdf libraries there is one executable > >>nc-config > >> that gives information of current configuration of netcdf libraries. I > >> found that nc-config information is incorrect about netcdf libraries > >> and some flags. For example see the following > >> > >> $ nc-config --all > >> --cc -> icc > >> --cflags -> -I/home/khanb/temp/include -I/home/khanb/zlib/include > >> --libs -> -L/home/khanb/temp/lib -lnetcdf > >> > >> --cxx -> icpc > >> --has-c++ -> yes > >> > >> --fc -> ifort > >> --fflags -> -g -I/home/khanb/temp/include > >> --flibs -> -L/home/khanb/temp/lib -lnetcdff -lnetcdf > >> --has-f77 -> yes > >> --has-f90 -> yes > >> > >> --has-dap -> yes > >> --has-nc2 -> yes > >> --has-nc4 -> no > >> --has-hdf5 -> no > >> --has-hdf4 -> no > >> --has-pnetcdf-> no > >> --has-szlib -> > >> > >> --prefix -> /home/khanb/temp > >> --includedir-> /home/khanb/temp/include > >> --version -> netCDF 4.1.3 > >> --------------------------------------- > >> > >> In the above nc-config output locations for --cflags, --libs,--fflags, > >> --flibs, --prefix and --includedir are incorrect. The */temp/* directory > >> does not exist at all. I created this directory longtime ago and then > >> deleted it later on. After that i have compiled netcdf dozens of time. > >>Of > >> course i do make distclean and make clean before any compile but i > >> keep getting the same old directory paths for the flags and --prefix. > >> Could you please advise why nc-config keep giving me old netcdf paths > >> (that does not exist anymore) and how can i fix it. > > > >To update nc-config after compiling netCDF, you must run "make install" > >after > >"make check". Otherwise, the old installed version of all the libraries, > >executables, > >and documentation will not be replaced by the new versions you have built. > > > >Typically (depending on the permissions required to overwrite files unser > >the > >installation directory named in the --prefix option), you will have to > >run "make install" > >using sudo or root permissions. > > > >I hope this helps ... > > > >--Russ > > > > > >Russ Rew UCAR Unidata Program > >address@hidden http://www.unidata.ucar.edu > > > > > > > >Ticket Details > >=================== > >Ticket ID: ACV-125667 > >Department: Support netCDF > >Priority: Normal > >Status: Closed > > > > Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: ACV-125667 Department: Support netCDF Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.