OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update the documentation describing where the linker will attempt to locate plugins. 

PR 24262
	* ld.texi (-plugin): Correct the path used to locate linker
	plugins.
This commit is contained in:
Nick Clifton 2019-03-15 12:08:56 +00:00
parent 1c529385d9
commit 1c82ed745b
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ld/ChangeLog
View File

@ -1,3 +1,9 @@
2019-03-15 Nick Clifton <nickc@redhat.com>
PR 24262
* ld.texi (-plugin): Correct the path used to locate linker
plugins.
2019-03-13 Sudakshina Das <sudi.das@arm.com>
* NEWS: Document --pac-plt.

2
ld/ld.texi
View File

@ -846,7 +846,7 @@ Note that the location of the compiler originated plugins is different
from the place where the @command{ar}, @command{nm} and
@command{ranlib} programs search for their plugins. In order for
those commands to make use of a compiler based plugin it must first be
copied into the @file{$@{libdir@}/bfd-plugins} directory. All gcc
copied into the @file{$@{bindir@}/../lib/bfd-plugins} directory. All gcc
based linker plugins are backward compatible, so it is sufficient to
just copy in the newest one.