https://sourceware.org/bugzilla/show_bug.cgi?id=21702
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nickc at redhat dot com
--- Comment #2 from Nick Clifton <nickc at redhat dot com> ---
Hi Martin,
This is a build/system installation issue more than anything. Assuming
that ar has been configured with --enable-plugins set[1] then the problem
is that ar is not finding the plugin that it needs. They are two ways
that it can find the plugin. The first is via a command line option to ar
itself, vis: --plugin=<path-to-gcc-lto-plugin>. This is the better
solution, IMHO, although it does mean that you will have to update your
build framework.
The second method is that ar (and the other binutils that support plugins)
will look in the directory /usr/lib/bfd-plugins for the plugin. So if you
copy gcc's liblto_plugin into this directory everything should start to
work. I am not a fan of this method since it relies upon having admin
access on the build machine, and it is easy to forget that the directory
is there, and then have problems because an out of date plugin is being
used.
Cheers
Nick
[1] I am not familiar with Arch Linux, but I suspect that plugin support
is probably enabled. Most distributions do that now.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
