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.

diff --git a/ld/ChangeLog b/ld/ChangeLog
index d37865b4e1b2591f6244310c6a68e8dce9d39394..76e2c719bab4d8921e941f05740f27b26f956133 100644 (file)
--- a/ld/ChangeLog
+++ b/ld/ChangeLog
@@ -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.

diff --git a/ld/ld.texi b/ld/ld.texi
index 7447c6ea0bbd4a2d5a4739ccdde006dfc34d0dcb..0bcbec463fe10ec1933e5e95ffbecb891a89657c 100644 (file)
--- a/ld/ld.texi
+++ b/ld/ld.texi
@@ -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.