> Russ, > > On Jul 30, 2010, at 1:53 PM, Unidata netCDF Support wrote: > > > I'm surprised at this. fsync() is part of most Unix standards, and we > > have reports that netCDF 4.1.1 has been built on CentOS without using > > the --disable-fsync option to configure. Also as far as I know mysql > > and other open source database systems use fsync and run on CentOS. > > Can you point to a reference about lack of CentOS support for fsync? > > Is this for just a particular specific filesystem on CentOS? > > > You are probably right. On my system, the definition of fsync() in > <unistd.h> is protected by #if defined __USE_BSD || defined > __USE_XOPEN. I don't know why -D_XOPEN_SOURCE=600 didn't define > __USE_XOPEN. Maybe I wasn't paying close enough attention and I > messed up on this one. So it sounds like we've left out an #include <unistd.h> for building on Unix systems so the prototype will be visible. That's a fix we need to make. > If you like, I will run my Makefile on your next beta version. Can > you let me know how to get it, or how to sign up somewhere, like on a > mailing list? Sure, that would be useful. We announce beta releases on the address@hidden mailing list, which you can join here: http://www.unidata.ucar.edu/software/netcdf/docs/faq.html#maillist We also have a read-only svn tree of the current stable snapshot, which gets updated more frequently than beta releases: http://svn.unidata.ucar.edu/repos/netcdf/ but that's mostly for use by active developers. Thanks for your offer to help test on specific platforms. We can only test on a few combinations, and more is better ... --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: EAY-251393 Department: Support netCDF Priority: Normal Status: Closed
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.