Thread: Error when compiling screen, target arm-none-eabi
View Single Post
Old 09-25-2012, 10:28 AM   #33
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by ppoo View Post
@knc1: I still gets gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found
 and don't know how to fix it. Is there any arguments to disable it when compiling toolchain?
There probably is, but why not: -fno-use-linker-plugin when you don't want it?

Or, maybe just stop telling it to use the linker plug-in if you don't want it?
I.E: remove: -fuse-linker-plugin

I am probably not your best source of information on this subject.
Others here are much more experienced with these "new" tool-chain features than I.
Last edited by knc1; 09-25-2012 at 11:22 AM.
knc1 is offline   Reply With Quote