From 1c82ed745bec154a3cd8a8bbf36c5be5086041d5 Mon Sep 17 00:00:00 2001 From: Nick Clifton Date: Fri, 15 Mar 2019 12:08:56 +0000 Subject: [PATCH] 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. --- ld/ChangeLog | 6 ++++++ ld/ld.texi | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/ld/ChangeLog b/ld/ChangeLog index d37865b4e1..76e2c719ba 100644 --- a/ld/ChangeLog +++ b/ld/ChangeLog @@ -1,3 +1,9 @@ +2019-03-15 Nick Clifton + + PR 24262 + * ld.texi (-plugin): Correct the path used to locate linker + plugins. + 2019-03-13 Sudakshina Das * NEWS: Document --pac-plt. diff --git a/ld/ld.texi b/ld/ld.texi index 7447c6ea0b..0bcbec463f 100644 --- 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. -- 2.34.1