* LTO Depends-on Non-static Toolchain
@ 2017-10-12 20:09 Justin Chen
0 siblings, 0 replies; only message in thread
From: Justin Chen @ 2017-10-12 20:09 UTC (permalink / raw)
To: crossgcc
Hello,
What is the reason behind having LTO require a non-static toolchain?
Is this a work around for some bug within binutils/gcc? Or is this
something that should not work in theory?
commit 45512b003d04b5a89c5c3bb6b674683d82b87f42
Author: Alexey Neyman <stilor@att.net>
Date: Sat Feb 18 19:00:25 2017 -0800
Have LTO depend-on non-static builds
Loading a dynamic library (LTO plugin) from a static binary fails
on ArchLinux. It is also prone to break if a system is ever upgraded.
Also, disable plugins if not enabled explicitly.
Signed-off-by: Alexey Neyman <stilor@att.net>
diff --git a/config/cc/gcc.in.2 b/config/cc/gcc.in.2
index 8818de6..638bfe9 100644
--- a/config/cc/gcc.in.2
+++ b/config/cc/gcc.in.2
@@ -124,6 +124,7 @@ config CC_GCC_USE_GRAPHITE
config CC_GCC_USE_LTO
bool "Enable LTO"
default y
+ depends on ! STATIC_TOOLCHAIN
help
Enable the Link Time Optimisations.
Thanks,
Justin
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-10-12 20:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-10-12 20:09 LTO Depends-on Non-static Toolchain Justin Chen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).