[Bug lto/84934] Installing the lto plugin where binutils will look for it

2018-03-29 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84934 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug lto/84934] Installing the lto plugin where binutils will look for it

2018-03-20 Thread dilyan.palauzov at aegee dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84934 --- Comment #4 from Дилян Палаузов --- Oh, I have typed on this matter already in the past: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70345

[Bug lto/84934] Installing the lto plugin where binutils will look for it

2018-03-19 Thread dilyan.palauzov at aegee dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84934 --- Comment #3 from Дилян Палаузов --- For LLVM I filled the same request: https://bugs.llvm.org/show_bug.cgi?id=36802 .

[Bug lto/84934] Installing the lto plugin where binutils will look for it

2018-03-18 Thread dilyan.palauzov at aegee dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84934 --- Comment #2 from Дилян Палаузов --- Builind a linux from scratch system, doing everywhere "./configure && make install" shall work, taking all defaults into account. For gcc+LTO+binutils this does not work. While distros can adjust the

[Bug lto/84934] Installing the lto plugin where binutils will look for it

2018-03-18 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84934 --- Comment #1 from Andrew Pinski --- I think it is up to the distro/installer themselves to install the plugin in the correct location. Binutils might be installed in a fully differently directory structure as gcc is.