Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] rustc: disable for ARMV7A with EABI
Date: Tue, 27 Feb 2018 09:39:35 +0100	[thread overview]
Message-ID: <20180227093935.4be76eab@windsurf.lan> (raw)
In-Reply-To: <87zi3uq391.fsf@dell.be.48ers.dk>

Hello,

On Tue, 27 Feb 2018 08:51:38 +0100, Peter Korsgaard wrote:

>  > It looks like a better fix would be:  
> 
>  > config BR2_PACKAGE_HOST_RUSTC_ARCH_SUPPORTS
>  >         bool
>  >         # The pre-built Rust standard library is only available for the
>  >         # following architectures/ABIs, and is built against glibc.
>  >         default y if BR2_i386
>  >         default y if BR2_x86_64
>  >         default y if BR2_aarch64
>  > -       default y if BR2_arm && !BR2_ARM_CPU_ARMV4 && !BR2_ARM_CPU_ARMV5
>  > +	default y if BR2_ARM_CPU_ARMV6 || BR2_ARM_CPU_ARMV7A  
> 
> I agree that having positive logic would be nicer. It is a bit more
> complicated than this as we also should handle ARMV8A cores in ARM mode
> similar to how ve handle ARMV7A.
> 
> Care to send an updated patch on top of master doing that?

I was hoping that Eric would handle that :-)

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

  reply	other threads:[~2018-02-27  8:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 20:04 [Buildroot] [PATCH 1/1] rustc: disable for ARMV7A with EABI Eric Le Bihan
2018-02-26 22:43 ` Peter Korsgaard
2018-02-26 22:52 ` Thomas Petazzoni
2018-02-27  7:51   ` Peter Korsgaard
2018-02-27  8:39     ` Thomas Petazzoni [this message]
2018-02-27  8:57       ` Peter Korsgaard

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=20180227093935.4be76eab@windsurf.lan \
    --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