New: Buildroot GCC: -lto requires plugin support in ranlib
https://bugs.busybox.net/show_bug.cgi?id=7592
Summary: Buildroot GCC: -lto requires plugin support in ranlib
Product: buildroot
Version: 2014.08
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: syntheticpp at gmx.net
CC: buildroot at uclibc.org
Estimated Hours: 0.0
To circumvent linker errors when lto is enabled I use arm-linux-gcc-ranlib and arm-linux-gcc-ar
but arm-linux-gcc-ranlib stops with this error:
sorry - this program has been built without plugin support
Config:
BR2_arm=y
BR2_cortex_a8=y
BR2_ARM_EABIHF=y
BR2_ARM_FPU_VFPV3=y
BR2_DEPRECATED=y
BR2_OPTIMIZE_3=y
BR2_TOOLCHAIN_BUILDROOT_EGLIBC=y
BR2_EGLIBC_VERSION_2_19=y
BR2_BINUTILS_VERSION_2_24=y
BR2_GCC_VERSION_4_9_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
[Buildroot] [Bug 7592] Buildroot GCC: -lto requires plugin support in ranlib
https://bugs.busybox.net/show_bug.cgi?id=7592
--- Comment #1 from Thomas Petazzoni <[email protected]> 2014-11-07 07:28:23 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.
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
[Buildroot] [Bug 7592] Buildroot GCC: -lto requires plugin support in ranlib
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7592
--- Comment #2 from syntheticpp at gmx.net 2014-11-09 10:54:30 UTC --- 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.
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
[Buildroot] [Bug 7592] Buildroot GCC: -lto requires plugin support in ranlib
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7592
--- Comment #3 from syntheticpp at gmx.net 2014-11-09 11:11:20 UTC --- 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)
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
[Buildroot] [Bug 7592] Buildroot GCC: -lto requires plugin support in ranlib
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7592
--- Comment #4 from syntheticpp at gmx.net 2014-11-09 12:14:18 UTC --- I pushed patches to the list to support lto for buildroot-clients. buildroot itself is still compiled without lto.
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
[Buildroot] [Bug 7592] Buildroot GCC: -lto requires plugin support in ranlib
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7592
--- Comment #5 from syntheticpp at gmx.net 2014-11-24 18:19:25 UTC ---
http://patchwork.ozlabs.org/patch/408558/
http://patchwork.ozlabs.org/patch/411183/
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
[Buildroot] [Bug 7592] Buildroot GCC: -lto requires plugin support in ranlib
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7592
--- Comment #6 from syntheticpp at gmx.net 2015-02-12 09:10:10 UTC --- Why does nobody care about this patch?
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
[Buildroot] [Bug 7592] Buildroot GCC: -lto requires plugin support in ranlib
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7592
--- Comment #7 from syntheticpp at gmx.net 2015-02-14 08:11:12 UTC --- Ah! didn't noticed
http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/103000/focus
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
[Buildroot] [Bug 7592] Buildroot GCC: -lto requires plugin support in ranlib
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7592
--- Comment #8 from syntheticpp at gmx.net 2015-02-18 10:37:22 UTC --- Updated patch:
http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/106748
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
[Buildroot] [Bug 7592] Buildroot GCC: -lto requires plugin support in ranlib
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7592
Thomas Petazzoni <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED--- Comment #9 from Thomas Petazzoni <[email protected]> 2015-06-04 15:15:44 UTC --- 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.
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.