From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: alexandre.belloni@bootlin.com,
Sreejith Ravi <sreejith.ravi087@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] package.py: Add Requires.private field in process_pkgconfig
Date: Thu, 27 Jun 2024 14:28:52 +0100 [thread overview]
Message-ID: <aac6891416a1c458f3156bbc2ab6e46c2178f1aa.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240627092915d7c0fb2b@mail.local>
On Thu, 2024-06-27 at 11:29 +0200, Alexandre Belloni via
lists.openembedded.org wrote:
> I believe this causes the following reproducibility failures:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4998/steps/13/logs/stdio
>
> https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20240627-3tyeozgn/packages/diff-html/
>
This is exposing a problem with the way we're handling python library
functions and their effect or lack of effect on the task hashes.
If you do something like:
bitbake libdrm -S none
then look at
bitbake-dumpsig tmp/stamps/core2-64-poky-linux/libdrm/2.4.120.do_package.sigdata.*
you'll see:
List of dependencies for variable oe.package.process_pkgconfig is ['PACKAGES', 'PKGDEST', 'SHLIBSDIRS', 'SHLIBSWORKDIR']
List of dependencies for variable package_do_pkgconfig is ['oe.package.process_pkgconfig']
Variable package_do_pkgconfig value is oe.package.process_pkgconfig(pkgfiles, d)
Variable oe.package.process_pkgconfig value is
i.e. it knows the function is being used but isn't caching its value.
That was by design but it does mean when you change funcitonality, you
have to manually tweak the tashhash which I'm not sure is a great idea
when put like this.
I'm pondering the best way to improve/fix this.
Cheers,
Richard
prev parent reply other threads:[~2024-06-27 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 14:05 [PATCH] package.py: Add Requires.private field in process_pkgconfig Sreejith Ravi
2024-06-27 9:29 ` [OE-core] " Alexandre Belloni
2024-06-27 13:28 ` Richard Purdie [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=aac6891416a1c458f3156bbc2ab6e46c2178f1aa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sreejith.ravi087@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox