Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Oscar Gomez Fuente <oscargomezf@gmail.com>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] How to select python-cryptograhy package
Date: Mon, 23 May 2022 18:38:58 +0300	[thread overview]
Message-ID: <87ilpwp82x.fsf@tarshish> (raw)
In-Reply-To: <CALtfCQY1a6sjLNUh42zsrsu1hPLTMHNDj4+5v5k8w8kv8u6tmg@mail.gmail.com>

Hi Oscar,

On Mon, May 23 2022, Oscar Gomez Fuente wrote:
> On Mon, 23 May 2022 at 05:50, Baruch Siach <baruch@tkos.co.il> wrote:
>> So BR2_HOSTARCH should be "x86_64". Is that what you see when you lookup
>> BR2_HOSTARCH in menuconfig?
>
> YES

It turns out I mixed BR2_PACKAGE_HOST_RUSTC_ARCH_SUPPORTS with
BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS. BR2_PACKAGE_PYTHON_CRYPTOGRAPHY
depends on the latter, and that in turn can only be enabled for musl or
glibc. The default libc in Buildroot is uClibc-ng. So you must select a
toolchain with musl or glibc to enable BR2_PACKAGE_PYTHON_CRYPTOGRAPHY.

Sorry for my confusion.

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-05-23 15:44 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 [this message]
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
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=87ilpwp82x.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --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