Hi John,
I have no objections, a great idea I think. Although it might be better to
make it a separate option (say -lfs) so that if there are problems on some
machines it can be easily disabled. I believe it adds large file support
to
fortran programs as well as C programs so will probably be good for
sander.
I assume it will only be needed for the IA32 machines. It might be nice to
know if specifying it on a 64 bit machine is benign though.
All the best
Ross
/\
\/
|\oss Walker
| Department of Molecular Biology TPC15 |
| The Scripps Research Institute |
| Tel: +1 858 784 8889 | EMail:- ross.rosswalker.co.uk |
|
http://www.rosswalker.co.uk | PGP Key available on request |
Note: Electronic Mail is not secure, has no guarantee of delivery, may not
be read every day, and should not be used for urgent or sensitive issues.
> -----Original Message-----
> From: owner-amber-developers.scripps.edu
> [mailto:owner-amber-developers.scripps.edu] On Behalf Of John Mongan
> Sent: Saturday, December 03, 2005 18:36
> To: amber-developers.scripps.edu
> Subject: amber-developers: Large File Support
>
> Does anyone have any objection to me changing configure so that our C
> based programs will be compiled with large file support (LFS)? This
> would involve adding the following to CFLAGS:
>
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
>
> When compiled this way, C programs (probably ptraj is the
> only one where
> it really matters) on modern 32-bit *nix platforms can work
> with files
> >2GB. This definitely works for ptraj on 32 bit linux. This
> should also
> work on modern non-linux platforms (those that have LFS), but I don't
> have access to any to test. On older platforms, it should
> have no effect.
>
> (Note: this is orthogonal to the binary trajectory work I mentioned
> earlier.)
>
> Thoughts/discussion?
>
> Thanks,
>
> John
>
Received on Wed Apr 05 2006 - 23:49:46 PDT
