From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] trousers: Pass "-mno-compact-casesi" when building for ARCv1
Date: Tue, 22 Nov 2016 11:03:05 +0100 [thread overview]
Message-ID: <20161122110305.5088f8ec@free-electrons.com> (raw)
In-Reply-To: <1479808825-2001-1-git-send-email-vzakhar@synopsys.com>
Hello,
On Tue, 22 Nov 2016 13:00:25 +0300, Vlad Zakharov wrote:
> Compact casesi patterns don't have a reload version. This causes build
> failures of "trousers" package for ARC.
>
> Current patch disables compact casesi patterns for ARCv1 (750D and 770D)
> via passing "-mno-compact-casesi" option when compiling "trousers".
>
> This change is a temporary workaround and the feature is going to be
> fixed in the next ARC toolchain release version.
>
> Signed-off-by: Vlad Zakharov <vzakhar@synopsys.com>
Has this been detected by the autobuilders? If yes, what is the
reference to the autobuilder failure?
> diff --git a/package/trousers/trousers.mk b/package/trousers/trousers.mk
> index 3d9e0ba..c5878df 100644
> --- a/package/trousers/trousers.mk
> +++ b/package/trousers/trousers.mk
> @@ -18,6 +18,10 @@ ifeq ($(BR2_PACKAGE_LIBICONV),y)
> TROUSERS_DEPENDENCIES += libiconv
> endif
>
> +ifeq ($(BR2_arc770d)$(BR2_arc750d),y)
> +TROUSERS_CONF_ENV += CFLAGS="$(CFLAGS) -mno-compact-casesi"
This should be:
CFLAGS="$(TARGET_CFLAGS) ..."
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-22 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 10:00 [Buildroot] [PATCH] trousers: Pass "-mno-compact-casesi" when building for ARCv1 Vlad Zakharov
2016-11-22 10:03 ` 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=20161122110305.5088f8ec@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