| Summary: | Buildroot GCC: -lto requires plugin support in ranlib | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | syntheticpp |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | buildroot |
| Priority: | P5 | ||
| Version: | 2014.08 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
syntheticpp
2014-11-04 11:28:59 UTC
We don't have LTO support right now in Buildroot. There is a patch adding LTO support (see http://patchwork.ozlabs.org/patch/362034/), but we not entirely happy with it yet, so it hasn't been applied. Feel free to test it and report back: some feedback on the patch would be very useful. So, I'm tempted to classify this bug not as a bug, but as a feature request. OK, I build gcc and binutils with + --enable-plugins \ + --enable-lto rootfs builds fine, but when gcc-ar is called it fails because it is also called with all the GCC options. The problem is that arm-linux-gcc-ar/ranlib are also wrapped by ext-toolchain-wrapper. When those tools just link to the external toolchain lto works (without switching to gold) I pushed patches to the list to support lto for buildroot-clients. buildroot itself is still compiled without lto. Why does nobody care about this patch? Ah! didn't noticed http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/103000/focus This has actually been fixed a long time ago, in commit 814f63ec32585f281855587fe0a287cee32e4232, which adds LTO support. It makes sure the wrapper is not generated for tools that shouldn't be wrapped. |