<stephen.pascoe@xxxxxxxxxx> writes:
> Hi Ed,
>
> Can I ask why the option exists if it shouldn't be used? Is it going
> to go away in the future or will it be fixed. I have used --with-FOO
> in preference to setting the environment under the assumption that it
> is more robust and I think that's a reasonable assumption.
>
> Thanks,
> Stephen.
>
> ---
> Stephen Pascoe +44 (0)1235 445980
> Centre of Environmental Data Archival
> STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK
>
Howdy Stephen!
The --with-hdf5 option has been removed from 4.1.3 (the current release)
and will not be in any future releases.
It might seem more robust, but it is not. It fails badly in the area of
32/64 bit platforms (i.e. platforms that want both a 32 bit and a 64 bit
version of the library installed at the same time.) It also adds a lot
of code to our build system.
The correct way to solve this is with the environment variables, which
leaves full control in the hands of the hands of the user.
The use of the --with options was an plot perpetrated by my evil twin,
who hates netCDF and all it stands for. He roams the Earth, attempting
to convince scientists to store their data in undocumented binary
formats. It makes for an awkward Thanksgiving dinner, but that's family
for you.
Thanks,
Ed
--
Ed Hartnett -- ed@xxxxxxxxxxxxxxxx
