This happens typically in a cygwin build, I saw it on my box too.
You have to tell the build system what an INT_MAX64 is supposed to
be, eg. add a define in your makefile for your machine:
Ray,
I did apply all patches chronologically. (sorry for not being clear about
it)
with such a large time distance, it is usually better to simply
download a full archive. you save yourself a lot of trouble.
if you insist on patches for whatever unknown reason, you have to do
more than what you have done.
you will need to execute:
make no-all
then apply the patches, then:
make purge
make clean-all
and then you should first try to compile with:
make serial
and/or
make mpi
some of the build mechanism was changed, so you will likely need to
adapt any custom make files (which should now be placed in
src/MAKE/MINE)
the whole patching/upgrade process is significantly easier when
following the svn or git repository. if you do your own development,
using git is highly recommended, as it allows you running and
maintaining your own local branches to which you can then merge in
from upstream repeatedly.
[...]
Then I tried to download the lateset stable release and build it, but
another error showed up when executing 'make':
error: identifier "INT64_MAX" is undefined
Anyone encountered these ?
are you building with a 32-bit compiler? then you should try to also
define -DLAMMPS_SMALLSMALL
unless you need to run extremely large systems (which usually require
supercomputers anyway), this would be sufficient and may be faster,
since it would requires less storage, offer more cache efficiency and
not require to emulate 64-bit integers on a 32-bit platform.