All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] rust: Disable 64bit atomics on crossbeam on riscv32
Date: Fri, 21 Oct 2022 13:10:28 -0700	[thread overview]
Message-ID: <CAMKF1sq0MegC9YtJc0WfWuvw5reHFBE+ugW_q9UTpVX_oaSYrg@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj-UfuhCnDKm9N1Y4CGtTeamQtPOTOhzmqQxVhZo9_+g=Q@mail.gmail.com>

On Fri, Oct 21, 2022 at 10:28 AM Alexander Kanavin
<alex.kanavin@gmail.com> wrote:
>
> On Fri, 21 Oct 2022 at 19:16, Khem Raj <raj.khem@gmail.com> wrote:
>
> > anyway, the builds failed at exactly the same point so as I sensed it
> > does not work.
>
> You need to find out why though. Upstream maintains a list, and we
> need to use it, and not duplicate it piecemeal.

It needs to be mapped or added. I have sent a patch to add OE's
understanding of target arch.

>
> Alex


  reply	other threads:[~2022-10-21 20:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 22:30 [PATCH] rust: Disable 64bit atomics on crossbeam on riscv32 Khem Raj
2022-10-21  6:03 ` [OE-core] " Alexander Kanavin
2022-10-21 14:05   ` Khem Raj
2022-10-21 15:41     ` Alexander Kanavin
2022-10-21 16:06       ` Khem Raj
2022-10-21 16:18         ` Alexander Kanavin
2022-10-21 16:59           ` Khem Raj
2022-10-21 17:12             ` Alexander Kanavin
2022-10-21 17:16               ` Khem Raj
2022-10-21 17:28                 ` Alexander Kanavin
2022-10-21 20:10                   ` Khem Raj [this message]
2022-10-22 19:56 ` Alexander Kanavin
     [not found] ` <17207C5BC457528C.2993@lists.openembedded.org>
2022-10-25 16:15   ` Alexander Kanavin
2022-10-26  0:45     ` Khem Raj
2022-10-26  7:58       ` Alexander Kanavin
2022-10-26 13:12         ` Khem Raj

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=CAMKF1sq0MegC9YtJc0WfWuvw5reHFBE+ugW_q9UTpVX_oaSYrg@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.