From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Antoine Coutant <antoine.coutant@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-rpds-py: bump to version 0.16.2
Date: Tue, 6 Feb 2024 15:53:14 +0100 [thread overview]
Message-ID: <ZcJH2rjRQQwKTbyN@landeda> (raw)
In-Reply-To: <1dd4afa6-e225-4e79-bb3a-21d0e04c7571@smile.fr>
Antoine, All,
On 2024-02-06 15:09 +0100, Antoine Coutant spake thusly:
> On 11/01/2024 06:17, James Hilliard wrote:
> > Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
[--SNIP--]
> > -PYTHON_RPDS_PY_VERSION = 0.12.0
> > +PYTHON_RPDS_PY_VERSION = 0.16.2
> rpds depends on the crate pyo3. This crate uses
> "std::sync::atomic::AtomicI64" which doesn't exist for 32 bits
> targets. That leads to an error [1].
I have been discussing this with Romain IRL, and he explained that the
issue _already_ happenned with 0.12.0, so this is not a regression and
thus reverting this patch will not fix the issue.
Is that correct?
Also, will std::sync::atomic::AtomicI64 ever be available for 32-bit
targets? If not, would that be considered a bug in the std lib?
> An issue have been opened on pyo3's github [2]. A fix have been accepted [3]
> but it isn't in the last release. Thus, this version bump doesn't
> fix this problem.
> [1]: https://gitlab.com/buildroot.org/buildroot/-/jobs/6093854842
> [2]: https://github.com/PyO3/pyo3/issues/3614
> [3]: https://github.com/PyO3/pyo3/pull/3619
It is not going to be easy to carry this change as a patch in Buildroot:
it would require that we be able to patch a package during the vendoring
step.
In this case, we'd need to do the vendoring (because we need the pyo3
crate to be downloaded), then apply the patch (with mangled paths) to
add the new dependency, then restart the vendoring. In the generic case,
we'd even need to be able to repeat the process in case that new
dependency has to be patched and so on and so on... That's not going to
be easy, by far...
Meh...
We can't even update to a random sha1 from the rpds git tree, because
they do nit even have an update to switch to a newer (even if
unreleased) pyo3.
Meh, again...
Not sure what to do...
What about adding a dependency on BR2_ARCH_IS_64 to python-rpds-pym and
propagate that to all its dependencies?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-06 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 5:17 [Buildroot] [PATCH 1/1] package/python-rpds-py: bump to version 0.16.2 James Hilliard
2024-02-05 10:53 ` Arnout Vandecappelle via buildroot
2024-02-05 11:05 ` Arnout Vandecappelle via buildroot
2024-02-06 13:44 ` Yann E. MORIN
2024-02-06 13:43 ` Yann E. MORIN
2024-02-06 14:09 ` Antoine Coutant
2024-02-06 14:53 ` Yann E. MORIN [this message]
2024-02-06 16:00 ` Antoine Coutant
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=ZcJH2rjRQQwKTbyN@landeda \
--to=yann.morin.1998@free.fr \
--cc=antoine.coutant@smile.fr \
--cc=buildroot@buildroot.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