From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Oscar Gomez Fuente <oscargomezf@gmail.com>,
Baruch Siach via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] How to select python-cryptograhy package
Date: Fri, 3 Jun 2022 16:03:06 +0200 [thread overview]
Message-ID: <20220603160306.00960433@windsurf> (raw)
In-Reply-To: <871qw5eu1l.fsf@tarshish>
On Fri, 03 Jun 2022 16:47:21 +0300
Baruch Siach <baruch@tkos.co.il> wrote:
> > I think this comment would be misleading. Indeed, based on this
> > comment, you could think that for this configuration (BR2_arm &&
> > BR2_ARM_CPU_ARMV8A && BR2_ARM_EABIHF && BR2_TOOLCHAIN_USES_GLIBC) we
> > would use the armv8-unknown-linux-gnueabihf variant of rustc, but
> > that's not the one we would be using.
>
> So what should be put in that comment? Just
> 'armv7-unknown-linux-gnueabihf' like we do for BR2_ARM_CPU_ARMV7A?
Maybe a bit more, to clarify that it's ARMv8 used in 32-bit mode, so we
use the armv7 Rust toolchain.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-06-03 14:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 15:25 [Buildroot] How to select python-cryptograhy package Oscar Gomez Fuente
2022-05-21 20:22 ` Baruch Siach via buildroot
2022-05-22 18:45 ` Oscar Gomez Fuente
2022-05-23 3:38 ` Baruch Siach via buildroot
2022-05-23 10:22 ` Oscar Gomez Fuente
2022-05-23 15:38 ` Baruch Siach via buildroot
2022-05-23 16:07 ` Oscar Gomez Fuente
2022-05-24 19:14 ` Baruch Siach via buildroot
2022-05-25 5:31 ` Oscar Gomez Fuente
2022-05-25 6:05 ` Baruch Siach via buildroot
2022-05-25 6:28 ` James Hilliard
2022-05-25 7:01 ` Baruch Siach via buildroot
2022-05-25 7:36 ` James Hilliard
2022-06-02 17:00 ` Thomas Petazzoni via buildroot
2022-06-03 13:47 ` Baruch Siach via buildroot
2022-06-03 14:03 ` Thomas Petazzoni via buildroot [this message]
2022-05-24 20:24 ` Fabio Estevam
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=20220603160306.00960433@windsurf \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=james.hilliard1@gmail.com \
--cc=oscargomezf@gmail.com \
--cc=thomas.petazzoni@bootlin.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