All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Fabio Estevam <festevam@gmail.com>,
	akuster808@gmail.com, Steve Sakoman <steve@sakoman.com>
Cc: openembedded-core@lists.openembedded.org,
	Bruce Ashfield <bruce.ashfield@gmail.com>
Subject: Re: [OE-core] [PATCH] perf: Depend on native setuptools3
Date: Tue, 1 Nov 2022 10:21:01 -0700	[thread overview]
Message-ID: <0d990cdc-e424-f4c9-007d-8a31c9149353@gmail.com> (raw)
In-Reply-To: <CAOMZO5BZQFHDYgA99ymw_zL12Qsmg9yzkLwqYRDUh5x53b9ZKg@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 668 bytes --]

On 11/1/22 10:11 AM, Fabio Estevam wrote:
> Hi Armin,
> 
> On Tue, Oct 11, 2022 at 12:02 AM Khem Raj <raj.khem@gmail.com> wrote:
>>
>> perf has need for python setuptools when scripting is enabled
>> from 6.0.0 onwards it seems to throw an explicit error
>>
>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>> Cc: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> This one landed in master:
> https://github.com/openembedded/openembedded-core/commit/da3d00178809bbf7cc453401e0c5937796ebc2c1
> 
> Could it be backported to kirkstone too?
> 
> I am facing an error when building a 6.0 kernel and this commit in
> master fixes it.
> 
> Thanks

+Steve


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2613 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]

  reply	other threads:[~2022-11-01 17:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  3:02 [PATCH] perf: Depend on native setuptools3 Khem Raj
2022-10-11 11:53 ` Bruce Ashfield
2022-11-01 17:11 ` [OE-core] " Fabio Estevam
2022-11-01 17:21   ` Khem Raj [this message]
2022-11-01 17:30     ` Steve Sakoman

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=0d990cdc-e424-f4c9-007d-8a31c9149353@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=akuster808@gmail.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=festevam@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=steve@sakoman.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.