LAMMPS WWW Site - LAMMPS Documentation - LAMMPS Mailing List Archives
Re: [lammps-users] keeping up with API changes for github version
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lammps-users] keeping up with API changes for github version

From: Giacomo Fiorin <giacomo.fiorin@...24...>
Date: Thu, 12 Apr 2018 11:52:41 -0400

Hi, did you use make package-update in the compilation procedure?

On Thu, Apr 12, 2018 at 11:17 AM, Noam Bernstein <noam.bernstein@...36.....4479...> wrote:
I just did a pull from the github repository, and that led to a compile time error.  The error appeared to be an incompatibility between fix_srp.cpp and neighbor.h:
../fix_srp.cpp: In member function ‘virtual void LAMMPS_NS::FixSRP::setup_pre_force(int)’:
../fix_srp.cpp:307:19: error: no matching function for call to ‘LAMMPS_NS::Neighbor::build()’
../fix_srp.cpp:307:19: note: candidate is:
In file included from ../fix_srp.cpp:27:0:
../neighbor.h:114:16: note: virtual void LAMMPS_NS::Neighbor::build(int)
   virtual void build(int);          // build all perpetual neighbor lists
../neighbor.h:114:16: note:   candidate expects 1 argument, 0 provided
Looks like that neighbor.h line was last touched on 2018-02-22, but the fix_srp.cp comes from USER-MISC, and the version in the actual compilation directory had not been updated.  

I was able to fix manually it by doing “make no-user-misc; make yes-user-misc”.  Is there a way of getting that to happen for all the optional items I’ve selected in the past? Could it be set up so it happened without user intervention?


Check out the vibrant tech community on one of the world's most
engaging tech sites,!
lammps-users mailing list

Giacomo Fiorin
Associate Professor of Research, Temple University, Philadelphia, PA
Contractor, National Institutes of Health, Bethesda, MD