From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7592] New: Buildroot GCC: -lto requires plugin support in ranlib
Date: Tue, 4 Nov 2014 11:29:01 +0000 (UTC) [thread overview]
Message-ID: <bug-7592-163@https.bugs.busybox.net/> (raw)
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
--
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.
next reply other threads:[~2014-11-04 11:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 11:29 bugzilla at busybox.net [this message]
2014-11-07 7:28 ` [Buildroot] [Bug 7592] Buildroot GCC: -lto requires plugin support in ranlib bugzilla at busybox.net
2014-11-09 10:54 ` bugzilla at busybox.net
2014-11-09 11:11 ` bugzilla at busybox.net
2014-11-09 12:14 ` bugzilla at busybox.net
2014-11-24 18:19 ` bugzilla at busybox.net
2015-02-12 9:10 ` bugzilla at busybox.net
2015-02-14 8:11 ` bugzilla at busybox.net
2015-02-18 10:37 ` bugzilla at busybox.net
2015-06-04 15:15 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-7592-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.