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

Re: 20050302: netCDF General - Large file problem

>To: address@hidden
>From: "Jim Cowie" <address@hidden>
>Subject: netCDF General - Large file problem
>Organization: RAL
>Keywords: 200503022003.j22K3ZjW025634

Jim,

> Thanks Russ, I just tried to put a sample file on our ftp server
> but apparently that system does not have LFS and the copy crapped
> out at 2GB. Let me try to rebuild the library (I think I'll get 3.5.1)
> from scratch and try again. I thought I was being pretty careful
> about linking with a large-file netcdf library but there are several
> netcdf libs floating around and I might have linked with one of
> those instead. I assume the compile flags I mentioned are correct,
> I setenv the CPPFLAGS env variable to these before running configure,
> and then I saw them on the compile line when I did make, so I think
> that worked right. I'll let you know what happens and if I can think
> of a place to put a sample file.

Yes, in general -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE work, but
not for all compilers or platforms.  For example for AIX, you have to
set different flags.

One advantage of the 3.6.0-p1 release is that the configure is
supposed to set the correct flags for large file support by default
for any platform and compiler combination, so you don't have to know
what flags to use.  With 3.5.1, it was up to the installer to get the
flags right.

We have platform-specific notes at

  
http://my.unidata.ucar.edu/content/software/netcdf/docs/netcdf-install/Platform-Specific-Notes.html
and output from our configure and build steps for various platforms
at:

  http://my.unidata.ucar.edu/content/software/netcdf/builds/index.html

but only for 3.6.0 and later, unfortunately.

--Russ