https://bugs.llvm.org/show_bug.cgi?id=36802
Bug ID: 36802
Summary: Install LLVMgold.so into {libdir}/bfd-plugins by
default
Product: tools
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: lto
Assignee: unassignedb...@nondot.org
Reporter: dilyan.palau...@aegee.org
CC: llvm-bugs@lists.llvm.org
As of 6.0, cmake compiles LLVMgold.so and puts it into {libdir}.
Doing "./configure && make install" for binutils, teaches ranlib, ar and nm to
scan by default {libdir}/bfd-plugins alphabetically and the first plugin, that
claims the object is used.
For the LTO primetime to arise, doing everywhere just "./configure && make
install" or the alternative cmake process, shall provide reasonable defaults.
In the concrete case, ar/nm/ranlib by default search in
/usr/local/lib/bfd-plugins , so llvm's `make install` shall put there
LLVMgold.so, unless asked to do something else.
Currently users detect in autoconf if they will do LTO, then switch
ar/nm/ranlib to gcc-ar/gcc-nm/gcc-ranlib in order to avoid dealing with the
--plugin and because they are unaware of the bfd-plugin directory. This is
unacceptable. This of course does not work, if gcc is not installed on the
system, but ar/ranlib/nm would work when the plugins are properly installed.
For GCC I filled the same request at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84934.
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
