Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] blktrace fails to build on ARC
Date: Sat, 15 Sep 2018 15:35:43 +0200	[thread overview]
Message-ID: <20180915153543.7418ad90@windsurf> (raw)
In-Reply-To: <28CDE50B11B27541A655A517CC37BFF38DDDAA@de02wembxa.internal.synopsys.com>

Hello Evgeniy,

On Sat, 15 Sep 2018 13:23:42 +0000, Evgeniy Didin wrote:

> Recently due to a patch
> https://git.busybox.net/buildroot/commit/?id=5a3f78c9191595f7ea9fab49360dfc18a743d28b
> some packages were enabled for ARC. Four of them (blktrace, lvm2,
> gadgetfs-test and libioo) are building with error, which points to
> some issues with "millicode" optimizations in toolchain, which had
> not occurred before. Currently we are studying this problem.

OK, thanks!

>  As a temporal solution until the issue is not resolved these
> packages can be disabled for ARC or millicode optimizations can be
> disabled for ARC by adding such lines in package/Makefile.in:
>
> --------------------------8<-------------------------------
> ifeq ($(BR2_arc),y)
> TARGET_ABI += -mno-millicode
> endif
> -------------------------->8----------------------------  
> What  will be the best solution?

Do we really want to pass -mno-millicode to all packages? If only four
packages are affected, what about adding this workaround to just those
four packages?

Also, will you remember to remove this workaround in the future when the
toolchain issue is fixed ? :-)

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-09-15 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13  7:50 [Buildroot] blktrace fails to build on ARC Thomas Petazzoni
2018-09-15 13:23 ` [Buildroot] [arc-buildroot] " Evgeniy Didin
2018-09-15 13:35   ` 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=20180915153543.7418ad90@windsurf \
    --to=thomas.petazzoni@bootlin.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