Hi Rorik,
Have just updated my source and run configure.
when running it doesn't seem to be reading the environment vars NETCDF_INC and NETCDF_LIB . In order to set them I had to do it on the command line
e.g configure NETCDF_LIB=/blah NETCDF_INC=/foo .
Is this behaviour intended ?
regards Henry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sort of surprised. configure parses the command line after it, so what you have should have worked. No, that behavior is not intended. configure does check that the directory you specified exists and won't add it to LDFLAGS unless it does. However, you should get a warning when this happens.
<snip>
checking whether the compiler has valarray<T>... yes
*** NETCDF_LIB location "/blah" does not exist. ***
*** NETCDF_INC location "/foo" does not exist. ***
configure: checking default compiler flags
<snip>
If you send me config.log, I'll take a look and try to fix it. Thanks.
rorik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Rorik,
Have just updated my source and run configure.
when running it doesn't seem to be reading the environment vars NETCDF_INC and NETCDF_LIB . In order to set them I had to do it on the command line
e.g configure NETCDF_LIB=/blah NETCDF_INC=/foo .
Is this behaviour intended ?
regards Henry
I'm sort of surprised. configure parses the command line after it, so what you have should have worked. No, that behavior is not intended. configure does check that the directory you specified exists and won't add it to LDFLAGS unless it does. However, you should get a warning when this happens.
<snip>
checking whether the compiler has valarray<T>... yes
*** NETCDF_LIB location "/blah" does not exist. ***
*** NETCDF_INC location "/foo" does not exist. ***
configure: checking default compiler flags
<snip>
If you send me config.log, I'll take a look and try to fix it. Thanks.
rorik