Hi Daniel,
With our move to GitHub, the 'tagged' releases are now packaged version
of the source, whereas before we prepared source packages uses the the
'make dist' command provided by autotools. The difference is that the
latter created the 'configure' script while the former does not.
In the short term, you may generate the necessary scripts by invoking
'autoreconf -i -f', or you can configure/build using 'cmake'
(instructions here:
http://www.unidata.ucar.edu/software/netcdf/docs/netCDF-CMake.html). I
am working on how to properly add the 'configure' script and other files
generated by autoreconf to the repository.
Sorry for the inconvenience,
-Ward
On 8/9/13 10:30 AM, Daniel Packman wrote:
I don't see the top level "configure" script after unpacking netcdf 4.3.0.
Are we supposed to create this via "autoconf"? I tried this and got
configure.ac:39: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
I blindly forged ahead and ran configure getting this error message:
configure: netCDF 4.3.0
configure: error: cannot find install-sh or install.sh in "." "./.." "./../.."
Suggestions are welcome.
_______________________________________________
netcdfgroup mailing list
netcdfgroup@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
