[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NetCDF configure

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: NetCDF configure
  • Date: Wed, 01 Oct 2003 13:53:29 -0600
James,

> > I will try to hire a student who knows about autoconf, automake, and
> > libtool, but if we can't, I don't know when we'll have this done.
> > It's the main thing holding up a netCDF 3.5.1 release, which is
> > currently in beta.
> 
> Well, I read this and figured I better do something. What I found was
> that we were using a collection of the macros and that only the
> UD_OUTPUT macro (which replaces autoconf's AC_OUTPUT) was causing a
> problem. The reason I used UD_OUTPUT was because the file
> fortran/nfconfig.inc needed it. The normal way for autoconf to build a
> header from a *.in file is to include a bunch of things in C-Style
> comments, something that I guess confuses FORTRAN compilers (I wonder
> when/if someone has a SOAP library for FORTRAN...). I hacked my
> configure.in to use the regular AC_OUTPUT macro and then filtered the
> nfconfig.inc file using sed. I'm all set.
> 
> I haven't wired up configure to run the script, but I remember that it's
> pretty easy to do. It seems the other macros in your aclocal.md work
> fine under autoconf 2.57. I'm using about five, so YMMV.

That's great, thanks for handling it.  It sounds like it may be easier
that I thought to move up to autoconf 2.5x ...

--Russ