public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bruce.ashfield@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/7] kernel-yocto: consolidated pull request
Date: Fri, 01 Jul 2022 15:49:37 +0100	[thread overview]
Message-ID: <694b9d319c6fa7a57807a188e5c8b27992a17e76.camel@linuxfoundation.org> (raw)
In-Reply-To: <16FDB9E325C9E889.5468@lists.openembedded.org>

On Fri, 2022-07-01 at 15:10 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Fri, 2022-07-01 at 13:52 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Fri, 2022-07-01 at 10:59 +0100, Richard Purdie via
> > lists.openembedded.org wrote:
> > > On Thu, 2022-06-30 at 15:16 -0400, bruce.ashfield@gmail.com wrote:
> > > > With conference travel and issues with meta-virtualization, I've been
> > > > behind in sending this out .. but I have been queueing changes, I just
> > > > wanted to be around in case something breaks.
> > > > 
> > > > Here are the -stable updates and the start of my efforts to bring
> > > > 5.19 in as the new reference kernel for the fall release.
> > > > 
> > > > lttng-modules needed it's normal tweaks to work against the 5.19 source,
> > > > but otherwise, nothing significant has popped up.  I have other parts
> > > > of that uprev under test (libc-headers, systemtap, etc).
> > > 
> > > Thanks Bruce!
> > > 
> > > Unfortunately there was one issue the autobuilder found, a
> > > reproducibility issue in perf:
> > > 
> > > http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220630-53gdlqxv/packages/diff-html/
> > > 
> > > I've not looked into it other than looking at the above link but it
> > > seems some python paths are creeping into the binaries.
> > 
> > This looked a little suspicious to me:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=18f2967418d031a390a5befe855dd0faa8af70b9
> 
> Confirmed that it is this change. Not sure why but at least we have an
> idea of where the isssue is.
> 
> I've also sent a patch to insane.bbclass to change WARN_QA such that we
> can detect this kind of issue much earlier in people's local builds. It
> may expose issues in other layers but those issues probably do need
> exposing at this point too...

This breaks:

override PYTHON := $(call get-executable-or-default,PYTHON,$(subst -config,,$(PYTHON_AUTO)))

as somehow PYTHON is expanded to a full path, yet:

override PYTHON := $(call get-executable-or-default,PYTHON,$(PYTHON_AUTO))

this works and doesn't expand PYTHON. I have no idea why, it doesn't
make sense.

Cheers,

Richard



  parent reply	other threads:[~2022-07-01 14:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 19:16 [PATCH 0/7] kernel-yocto: consolidated pull request bruce.ashfield
2022-06-30 19:16 ` [PATCH 1/7] linux-yocto/5.10: update to v5.10.121 Bruce Ashfield
2022-06-30 19:16 ` [PATCH 2/7] linux-yocto/5.15: update to v5.15.46 Bruce Ashfield
2022-06-30 19:16 ` [PATCH 3/7] linux-yocto/5.15: update to v5.15.48 bruce.ashfield
2022-06-30 19:16 ` [PATCH 4/7] linux-yocto/5.10: update to v5.10.123 bruce.ashfield
2022-06-30 19:16 ` [PATCH 5/7] linux-yocto-dev: bump to v5.19-rc bruce.ashfield
2022-06-30 19:16 ` [PATCH 6/7] linux-yocto/5.15: drop obselete GPIO sysfs ABI bruce.ashfield
2022-06-30 19:16 ` [PATCH 7/7] lttng-modules: fix 5.19+ build bruce.ashfield
2022-07-01  9:59 ` [PATCH 0/7] kernel-yocto: consolidated pull request Richard Purdie
     [not found] ` <16FDAC3178C621FE.2437@lists.openembedded.org>
2022-07-01 12:52   ` [OE-core] " Richard Purdie
     [not found]   ` <16FDB5A16CDF6390.2437@lists.openembedded.org>
2022-07-01 14:10     ` Richard Purdie
     [not found]     ` <16FDB9E325C9E889.5468@lists.openembedded.org>
2022-07-01 14:49       ` Richard Purdie [this message]
2022-07-01 14:57         ` Bruce Ashfield
2022-07-01 15:01           ` Richard Purdie
2022-07-01 15:15             ` 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=694b9d319c6fa7a57807a188e5c8b27992a17e76.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox