diff options
| author | Dan Albert <danalbert@google.com> | 2019-03-14 10:02:58 -0700 |
|---|---|---|
| committer | Dan Albert <danalbert@google.com> | 2019-03-14 10:02:58 -0700 |
| commit | 64be84b68e3fc8a5cc69ade13dfa32d08a015539 (patch) | |
| tree | 6bed4e246954d6e7defbdd5969530778bfe389eb /docs | |
| parent | 96c8c44198dbe4ae098dbc395d07432b27a0159f (diff) | |
| download | ndk-64be84b68e3fc8a5cc69ade13dfa32d08a015539.tar.gz | |
Fix typo in argument name in doc.
Fortunately the "useful arguments" part of the doc got this right.
Test: None
Bug: None
Change-Id: I6cc91202ff277d89a59b8642f9b68430d223274c
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/BuildSystemMaintainers.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/BuildSystemMaintainers.md b/docs/BuildSystemMaintainers.md index a2b1f182e..fde6fdfd6 100644 --- a/docs/BuildSystemMaintainers.md +++ b/docs/BuildSystemMaintainers.md @@ -458,8 +458,8 @@ these symbols from a shared library. If this library was built with the wrong unwinder, it is possible for one unwinder to call into the other. As they are not compatible, this will likely result in either a crash or a failed unwind. To avoid this problem, libraries should always be built with -`-Wl,--exclude-library,libgcc.a` and `-Wl,--exclude-library,libunwind.a` (the -latter is only necessary for 32-bit ARM) to ensure that unwind symbols are not +`-Wl,--exclude-libs,libgcc.a` and `-Wl,--exclude-libs,libunwind.a` (the latter +is only necessary for 32-bit ARM) to ensure that unwind symbols are not re-exported from shared libraries. Even with the above precautions, it is still possible for an improperly built |