From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: fix libgcc build for xtensa
Date: Fri, 24 Jul 2015 11:32:44 +0200 [thread overview]
Message-ID: <20150724113244.61809b39@free-electrons.com> (raw)
In-Reply-To: <1437730231-22278-1-git-send-email-jcmvbkbc@gmail.com>
Dear Max Filippov,
On Fri, 24 Jul 2015 12:30:31 +0300, Max Filippov wrote:
> xtensa libgcc can't be built with -mtext-section-literals flag, now
> coming from TARGET_CFLAGS, because it needs to emit literals to
> .init/.fini sections, which is not currently supported.
>
> Filter -mtext-section-literals flag out of GCC_COMMON_TARGET_CFLAGS.
>
> Suggested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
> package/gcc/gcc.mk | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-24 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 9:30 [Buildroot] [PATCH] package/gcc: fix libgcc build for xtensa Max Filippov
2015-07-24 9:32 ` Thomas Petazzoni [this message]
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=20150724113244.61809b39@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox