mirror of
git://git.savannah.gnu.org/libtool.git
synced 2025-02-11 15:00:08 +08:00
libtool: Fix typos
Typos found with codespell. * doc/libtool.texi: Change 'incompatabile' to 'incompatible'. * doc/notes.texi: Change 'neccesary' to 'necessary'.
This commit is contained in:
parent
fcaa75e5dc
commit
d6d4397dff
@ -5594,7 +5594,7 @@ running the @command{libtool} test cases.
|
||||
Tests @command{libtool}'s versioning system. Tests begin with verifying the
|
||||
behaviour of @command{libtool} versioning flags @option{-version-info} and
|
||||
@option{-version-number}. Next, this tests installing a library, then updating
|
||||
the library with a new revision, a compatible update, and an incompatabile
|
||||
the library with a new revision, a compatible update, and an incompatible
|
||||
update. In each case, the tests verify that the original library will link and
|
||||
install as expected.
|
||||
|
||||
|
@ -27,7 +27,7 @@ will generate the instantiations. For Portland pgCC version5, use
|
||||
@code{CXX='pgCC --one_instantiation_per_object'} and avoid parallel @command{make}.
|
||||
|
||||
@item
|
||||
For C++ code, it may be neccesary to specify a library if it is a dependency
|
||||
For C++ code, it may be necessary to specify a library if it is a dependency
|
||||
of a link/compile flag. For example in GNU G++, if you want to use
|
||||
@code{-fsanitize=address} you need to specify the @code{-lasan} library,
|
||||
like so: @code{g++ -o libx.la -fsanitize=address -lasan -rpath [...]}.
|
||||
|
Loading…
Reference in New Issue
Block a user