All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Gamblin <trevor.gamblin@windriver.com>
To: Ross Burton <ross@burtonini.com>, Tim Orling <ticotimo@gmail.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] python3-cryptography "success"
Date: Wed, 12 Jan 2022 14:36:53 -0500	[thread overview]
Message-ID: <f831104a-7f38-8e70-673d-0eb0dc43a1e3@windriver.com> (raw)
In-Reply-To: <CAAnfSTs7Uu5OHb3n6AikSHHr6b-t=fJyqbGBbVnSDaEdg_ttNQ@mail.gmail.com>


On 2022-01-12 08:04, Ross Burton wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
>
> On Wed, 12 Jan 2022 at 04:34, Tim Orling <ticotimo@gmail.com> wrote:
>> I finally cracked a nut that was at the root of our cross-compile woes with pyo3, which was the root cause of python3-cryptography not building.
>>
>> For those interested, my WIP branch is:
>> https://git.openembedded.org/meta-openembedded-contrib/log/?h=timo/python3-cryptography_36.0.1
> I've just built this on aarch64 host for aarch64 target, and it built
> successfully. Congratulations! :)

Tested qemux86-64 and qemuarm64 as well. Great work!

- Trevor

>
> Ross
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#94786): https://lists.openembedded.org/g/openembedded-devel/message/94786
> Mute This Topic: https://lists.openembedded.org/mt/88367097/3616776
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [trevor.gamblin@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


      reply	other threads:[~2022-01-12 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  4:34 python3-cryptography "success" Tim Orling
2022-01-12 13:04 ` [oe] " Ross Burton
2022-01-12 19:36   ` Trevor Gamblin [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=f831104a-7f38-8e70-673d-0eb0dc43a1e3@windriver.com \
    --to=trevor.gamblin@windriver.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=ross@burtonini.com \
    --cc=ticotimo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.