[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[netCDF #RZG-350418]: curl and configure options
- Subject: [netCDF #RZG-350418]: curl and configure options
- Date: Fri, 03 May 2019 14:05:55 -0600
[Dennis interjecting:
1. examining configure.ac, it looks like byterange is disabled by
default, so either you specified it, or there was some older
configure.ac that had it enabled by default and we later changed it.
2. What documentation did you look at that said to use --with-hdf5?
We need to fix that.
]
>
> Can you provide your config.log file, generated when you run configure? I am
> curious why you are getting this message. What happens if you run the same
> configure command, but passing the '--disable-byterange' argument as well as
> '--disable-dap'?
>
> Also, can you provide a link to the documentation referencing those arguments
> (--with-szlib, --with-hdf5, etc?). They are no longer necessary. Their
> locations are controlled using LDFLAGS, CFLAGS, etc.
>
> Thanks,
>
> -Ward
>
> > Hello,
> >
> > I am trying to build library netcdf-c-4.7.0. When running "configure" I
> > am getting a message "configure: error: curl required for byte range
> > support. Install curl or build without --enable-byterange.". But I am
> > not using the option "--enable-byterange". The options I use are "
> > --enable-netcdf-4 --enable-shared --prefix=... --disable-dap". Please
> > help to build the library without curl.
> >
> > Another question: when I try to use options "-with-zlib=...
> > --with-szlib=... --with-hdf5=..." the configure reports that these
> > options are not supported, which is contrary to online documentation.
> > Could you please clarify how it works now?
> >
> > Thanks,
> >
> > Alex
> >
> >
> >
> >
>
=Dennis Heimbigner
Unidata
Ticket Details
===================
Ticket ID: RZG-350418
Department: Support netCDF
Priority: Normal
Status: Open
===================
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.