This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/69790] New: LTO compiling GCC does not work (lib/bfd-plugin path has unclear location)
- From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 12 Feb 2016 21:18:42 +0000
- Subject: [Bug bootstrap/69790] New: LTO compiling GCC does not work (lib/bfd-plugin path has unclear location)
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69790
Bug ID: 69790
Summary: LTO compiling GCC does not work (lib/bfd-plugin path
has unclear location)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: dilyan.palauzov at aegee dot org
Target Milestone: ---
On my system, when I compile gcc using -flto -O3 (meaning LTO is applied to the
compiler) I face the problem, that liblto_plugin.so on my system is installed
under /usr/local/lib/bfd-plugins , where binutils accepts it. But nm compiled
during bootstrapping gcc looks for the plugins under
/usr/local/x86_64-pc-linux-gnu/lib/bfd-plugins .
nm compiled as part of binutils and as part of gcc should look at the same
location for gcc plugins.