This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Autoloading lto-plugin path
- From: "Serg Iv via binutils" <binutils at sourceware dot org>
- To: binutils at sourceware dot org
- Date: Tue, 22 Jan 2019 21:09:26 +0300
- Subject: Autoloading lto-plugin path
- Reply-to: Serg Iv <fishburgzone at mail dot ru>
Hi!
While building cross binutils (for creating win executables on linux) i
faced the issue that auto-loading LTO plugin won't work for me properly.
The doc says that ar, nm and so on autoload plugins from
${libdir}/bfd-plugins, but the only place where "bfd-plugins" is
mentioned is bfd/plugin.c, and here we have
plugin_dir = concat (BINDIR, "/../lib/bfd-plugins", NULL);
So, the plugins dir depends on BINDIR and doesn't depend on --libdir=...
actually. Am i right?
Excerpt from my building script
host="$arch-w64-mingw32"
./configure" --prefix="/usr" --target="$host" --libdir="/usr/$host/lib" ...
and i'm putting lto-plugins to /usr/$host/lib/bfd-plugins
Thanks.