Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Baruch Siach via buildroot <buildroot@buildroot.org>
Cc: buildroot@busybox.net, James Hilliard <james.hilliard1@gmail.com>,
	Oscar Gomez Fuente <oscargomezf@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/rustc: add support for ARMv8 with 32-bit software
Date: Sun, 19 Jun 2022 15:23:44 +0200	[thread overview]
Message-ID: <87o7yordlr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <875ykwsstd.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Sun, 19 Jun 2022 15:09:50 +0200")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

>>>>> "Baruch" == Baruch Siach via buildroot <buildroot@buildroot.org> writes:
 >> BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS is not enabled when ARMv8
 >> target hardware is combined with 32-bit software. That is because ARMv7
 >> (32-bit) toolchain is only enabled for BR2_ARM_CPU_ARMV7A which is
 >> mutually exclusive with BR2_ARM_CPU_ARMV8A.

 >> Use ARMv7 toolchain for 32-bit software.

 >> Cc: James Hilliard <james.hilliard1@gmail.com>
 >> Reported-by: Oscar Gomez Fuente <oscargomezf@gmail.com>
 >> Signed-off-by: Baruch Siach <baruch@tkos.co.il>

 > Committed to 2022.05.x, thanks.

.. and 2022.02.x.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-06-19 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 14:14 [Buildroot] [PATCH] package/rustc: add support for ARMv8 with 32-bit software Baruch Siach via buildroot
2022-06-09 20:33 ` Thomas Petazzoni via buildroot
2022-06-19 13:09 ` Peter Korsgaard
2022-06-19 13:23   ` Peter Korsgaard [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=87o7yordlr.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=buildroot@busybox.net \
    --cc=james.hilliard1@gmail.com \
    --cc=oscargomezf@gmail.com \
    /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