All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: Max Krummenacher <max.oss.09@gmail.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	Max Krummenacher <max.krummenacher@toradex.com>
Subject: Re: [oe][OE-core][Patch 0/2] perf: sort-pmuevents: some fixes
Date: Mon, 22 Nov 2021 20:39:30 -0500	[thread overview]
Message-ID: <CADkTA4NNawU1htCkTv9T-uEZ=-e82nKZG9yN9M9oO19B9VQLXQ@mail.gmail.com> (raw)
In-Reply-To: <CAEUSe7_pESAniiBwAv2oASHi6je67zf7sMw1F2TNcas_1raspA@mail.gmail.com>

On Mon, Nov 22, 2021 at 12:23 PM Daniel Díaz <daniel.diaz@linaro.org> wrote:
>
> Hello!
>
> On Mon, 22 Nov 2021 at 10:51, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
> > On Mon, Nov 22, 2021 at 11:35 AM Max Krummenacher <max.oss.09@gmail.com> wrote:
> [...]
> > > Note that the kernel itself doesn't build either as after 5.15 it now
> > > does try to run the dt_binding_check for which the kernel recipe does
> > > not provide whatever stuff is needed.
> > > I just did a revert patch for commit 53182e81f47d ("kbuild: Enable
> > > DT schema checks for %.dtb targets") to get over that.
> >
> > I have a fixefor that particular problem (the bindings),  so you can
> > safely continue to ignore it .. but I hadn't gotten around to fixing
> > perf yet.
> [...]
>
> I don't mean to hijack the subject, but do you have some quick
> pointers on that? We're seeing the same on linux-next and
> linux-mainline since that patch landed in those trees, and have

I'm trying to come up with a way to fix this without needing a kernel patch.

Sounds like you are already aware of the pkgconfig issue, which is
what I'm attempting to fix via environment manipulation versus a
patch.

We do need python dtschema as well, as a new native dependency of the
bindings check, which unfortunately pulls in ruamel and jsonschema.
Those are both in meta-python, so they need to migrate to core to
support the new checking.

There's also a problem with nproc being used, and it was giving me an
error on one of my servers, I haven't looked into it more yet.

I have a quick recipe here as well. And with those two pieces in
place, I'm up and running again.

The right thing for the short term, is that revert. There's quite a
bit of sorting out to do, to get this in decent shape for core ...
personally, I'd like to make the checking optional for those that
don't want it .. but that goes against what Rob is trying to do in the
kernel :D

If those issues sound familiar, and there's interest, I can drop my
WIP commits into a branch and share.

Bruce

> soft-reverted the commit for now. This (incomplete) recipe has not
> helped us get through that:
>
>   https://github.com/mrchapp/meta-lkft/blob/d/add-dtschema/recipes-devtools/python/dtschema_2021.10.bb
>
> Thanks and greetings!
>
> Daniel Díaz
> daniel.diaz@linaro.org


--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


  reply	other threads:[~2021-11-23  1:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 16:34 [oe][OE-core][Patch 0/2] perf: sort-pmuevents: some fixes Max Krummenacher
2021-11-22 16:34 ` [oe][OE-core][Patch 1/2] perf: sort-pmuevents: don't drop elements Max Krummenacher
2021-11-22 16:34 ` [oe][OE-core][Patch 2/2] perf: sort-pmuevents: allow for additional type qualifiers and storage class Max Krummenacher
2021-11-22 16:51 ` [oe][OE-core][Patch 0/2] perf: sort-pmuevents: some fixes Bruce Ashfield
2021-11-22 17:23   ` Daniel Díaz
2021-11-23  1:39     ` Bruce Ashfield [this message]
2021-11-23  5:05       ` Bruce Ashfield
2021-11-23  1:41 ` Bruce Ashfield
2021-11-23 13:48   ` Max Krummenacher
2021-11-23 13:55     ` Bruce Ashfield
2021-11-23 13:58       ` Max Krummenacher
2021-11-23 14:04         ` Bruce Ashfield
     [not found]         ` <16BA31E66A619EB2.13215@lists.openembedded.org>
2021-11-23 21:40           ` Bruce Ashfield

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='CADkTA4NNawU1htCkTv9T-uEZ=-e82nKZG9yN9M9oO19B9VQLXQ@mail.gmail.com' \
    --to=bruce.ashfield@gmail.com \
    --cc=daniel.diaz@linaro.org \
    --cc=max.krummenacher@toradex.com \
    --cc=max.oss.09@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.