aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohn S. Urban <urbanjost@comcast.net>2020-12-27 20:05:28 -0500
committerJohn S. Urban <urbanjost@comcast.net>2020-12-27 20:12:29 -0500
commit43d13460036df1ba1e520a5bc5936693264bef07 (patch)
tree0bf4169515f78d92fb4bbee347968ca97ac0d1b2
parent444f8d2342eb2503c3e531b9040f1a1835d5fc09 (diff)
downloadfpm-43d13460036df1ba1e520a5bc5936693264bef07.tar.gz
fpm-43d13460036df1ba1e520a5bc5936693264bef07.zip
errata
-rw-r--r--fpm/src/fpm/cmd/new.f908
-rw-r--r--fpm/src/fpm_command_line.f902
2 files changed, 5 insertions, 5 deletions
diff --git a/fpm/src/fpm/cmd/new.f90 b/fpm/src/fpm/cmd/new.f90
index 15c1dbe..a5647b3 100644
--- a/fpm/src/fpm/cmd/new.f90
+++ b/fpm/src/fpm/cmd/new.f90
@@ -245,9 +245,9 @@ character(len=:,kind=tfc),allocatable :: littlefile(:)
&' # have one library name or a list of strings in case several ',&
&' # libraries should be linked. This list of library dependencies is ',&
&' # exported to dependent packages. You may have to alter your library ',&
- &' # search-path to ensure the libraries can be accessed. Typically, ',&
+ &' # search-path to ensure the libraries can be accessed. Typically, ',&
&' # this is done with the LD_LIBRARY_PATH environment variable on ULS ',&
- &' # (Unix-Like Systems). You only specify the core name of the library ',&
+ &' # (Unix-Like Systems). You only specify the core name of the library ',&
&' # (as is typical with most programming environments, where you ',&
&' # would specify "-lz" on your load command to link against the zlib ',&
&' # compression library even though the library file would typically be ',&
@@ -413,7 +413,7 @@ character(len=:,kind=tfc),allocatable :: littlefile(:)
&' # Now lets begin entries for the TOML tables (lines beginning with "[[") ',&
&' # that describe the program sources -- applications, tests, and examples. ',&
&' # ',&
- &' # First we will configuration individual applications run with "fpm run". .',&
+ &' # First we will configuration individual applications run with "fpm run". ',&
&' # ',&
&' # + the "name" entry for the executable to be built must always ',&
&' # be specified. The name must satisfy the rules for a Fortran ',&
@@ -488,7 +488,7 @@ character(len=:,kind=tfc),allocatable :: littlefile(:)
&' ',&
&' # The same declarations can be made for test programs, which are ',&
&' # executed with the "fpm test" command and are not build when your ',&
- &' # package is used as a dependency by other packages. These are ',&
+ &' # package is used as a dependency by other packages. These are ',&
&' # typically unit tests of the package only used during package ',&
&' # development. ',&
&' ',&
diff --git a/fpm/src/fpm_command_line.f90 b/fpm/src/fpm_command_line.f90
index 6e331ae..c314183 100644
--- a/fpm/src/fpm_command_line.f90
+++ b/fpm/src/fpm_command_line.f90
@@ -849,7 +849,7 @@ contains
' demo.f90 ', &
' ', &
' Using this file structure is highly encouraged, particularly for ', &
- ' small packages primarily intended to be used as dependendencies. ', &
+ ' small packages primarily intended to be used as dependencies. ', &
' ', &
' If you find this restrictive and need to customize the package ', &
' structure you will find using the --full switch creates a ', &