ICODE-ADC/lammps
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix spelling

Browse Source
This commit is contained in:
Axel Kohlmeyer
2020-09-30 20:00:53 -04:00
parent a9b27caf17
commit dc13a61b40
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/Build_basics.rst
View File

@ -162,7 +162,7 @@ with compiler versions in use. If compilation with OpenMP enabled fails
because of your compiler requiring strict OpenMP 4.0 semantics, you can because of your compiler requiring strict OpenMP 4.0 semantics, you can
change the behavior by adding ``-D LAMMPS_OMP_COMPAT=4`` to the change the behavior by adding ``-D LAMMPS_OMP_COMPAT=4`` to the
``LMP_INC`` variable in your makefile, or add it to the command line ``LMP_INC`` variable in your makefile, or add it to the command line
while configuring with CMake. LAMMPS will autodetect a suitable setting while configuring with CMake. LAMMPS will auto-detect a suitable setting
for most GNU, Clang, and Intel compilers. for most GNU, Clang, and Intel compilers.
---------- ----------

2
doc/src/Library.rst
View File

@ -81,7 +81,7 @@ and consequently the function :cpp:func:`lammps_open` may not be used.
No checks are made on the arguments of the function calls of the C No checks are made on the arguments of the function calls of the C
library interface. *All* function arguments must be non-NULL unless library interface. *All* function arguments must be non-NULL unless
*explicitly* allowed, and msut point to consistent and valid data. Buffers *explicitly* allowed, and must point to consistent and valid data. Buffers
for storing returned data must be allocated to a suitable size. for storing returned data must be allocated to a suitable size.
Passing invalid or unsuitable information will likely cause crashes Passing invalid or unsuitable information will likely cause crashes
or corrupt data. or corrupt data.