bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/20343] Document how to use LTO


From: dilyan.palauzov at aegee dot org
Subject: [Bug binutils/20343] Document how to use LTO
Date: Sun, 10 Jul 2016 18:17:27 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=20343

--- Comment #3 from dilyan.palauzov at aegee dot org <dilyan.palauzov at aegee 
dot org> ---
The bfd-plugins directory is not documented.

Doing "gcc -c t.c" "strace nm --plugin=liblto_plugin.so.0.0.0 t.o" does not
show that the bfd-plugins directory is checked, nor does "strace ar csr
--plugin liblto_plugin.so.0.0.o libt.a t.o" check it.

I use binutils 2.26.51.20160709 with ./configure --prefix=/usr/local.  I guess
the bfd-plugins directory has to be somewhere under /usr/local
(/usr/local/lib/bfd-plugins or /usr/local/x86_64-pc-linux-gnu/lib/bfd-plugins),
but strace does not show anything under local, except
execve("/usr/local/{ar,nm}")

Why is here:

open("/lib/x86_64-linux-gnu/tls/x86_64/liblto_plugin.so.0.0.o",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/tls/liblto_plugin.so.0.0.o", O_RDONLY|O_CLOEXEC) =
-1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/x86_64/liblto_plugin.so.0.0.o", O_RDONLY|O_CLOEXEC)
= -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/liblto_plugin.so.0.0.o", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
open("/usr/lib/x86_64-linux-gnu/tls/x86_64/liblto_plugin.so.0.0.o",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/x86_64-linux-gnu/tls/liblto_plugin.so.0.0.o",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/x86_64-linux-gnu/x86_64/liblto_plugin.so.0.0.o",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/x86_64-linux-gnu/liblto_plugin.so.0.0.o", O_RDONLY|O_CLOEXEC) =
-1 ENOENT (No such file or directory)


used "x86_64-linux-gnu" instead of "x86_64-pc-linux-gnu"

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]