Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Gamblin <tgamblin@baylibre.com>
To: Ross Burton <Ross.Burton@arm.com>,
	Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	openembedded-core <openembedded-core@lists.openembedded.org>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core][PATCH] python3-numpy: upgrade 1.26.4 -> 2.1.2
Date: Mon, 4 Nov 2024 09:24:17 -0500	[thread overview]
Message-ID: <b76706a2-11a6-4615-baaf-dec8fcb4d7bf@baylibre.com> (raw)
In-Reply-To: <13BF7241-1A92-4653-B4B9-FEA628356BE1@arm.com>


On 2024-11-04 09:20, Ross Burton wrote:
> On 1 Nov 2024, at 21:47, Ross Burton <Ross.Burton@arm.com> wrote:
>> On 1 Nov 2024, at 10:08, Alexander Kanavin via lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org> wrote:
>>> 2. The second issue is slightly trickier. There's a number of
>>> generated c files produced by cython and they contain lines like:
>>>
>>> static const char __pyx_k_srv_storage_alex_yocto_build_64[] =
>>> "/srv/storage/alex/yocto/build-64/tmp/work/core2-64-poky-linux/python3-numpy/2.1.2/numpy-2.1.2/numpy/random/bit_generator.pyx";
>>> PyObject *__pyx_kp_s_srv_storage_alex_yocto_build_64;
>>> etc.
>>>
>>> This needs to be fixed by tracking down where in cython this stuff is
>>> generated, and replacing real paths (or parts of them) with something
>>> reproducible, like 'reproducible_build_path' or similar. Then this
>>> should be submitted or raised with upstream.
> I’ve got a prototype patch that fixes this in cython itself, meaning a pretty large chunk of horrible code in recipes (that silenced the buildpath warnings,  but didnt actually fix reproduciblity) can be removed.  I’ll hopefully get it good enough to post today.
Let me know if you want help testing - I started looking at the PR you 
mentioned over the weekend but didn't get anywhere yet.
>
> Ross


  reply	other threads:[~2024-11-04 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 19:37 [OE-core][PATCH] python3-numpy: upgrade 1.26.4 -> 2.1.2 Trevor Gamblin
2024-10-30 14:22 ` Mathieu Dubois-Briand
2024-11-01 10:08   ` Alexander Kanavin
2024-11-01 13:17     ` Trevor Gamblin
2024-11-01 21:47     ` Ross Burton
2024-11-04 14:20       ` Ross Burton
2024-11-04 14:24         ` Trevor Gamblin [this message]
2024-11-05 16:17     ` Ross Burton

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=b76706a2-11a6-4615-baaf-dec8fcb4d7bf@baylibre.com \
    --to=tgamblin@baylibre.com \
    --cc=Ross.Burton@arm.com \
    --cc=alex.kanavin@gmail.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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