dev-util/maturin-1.2.3 includes and executes a binary blob at ${WORKDIR}/cargo_home/gentoo/serde_derive-1.0.183/serde_derive-x86_64-unknown-linux-gnu This should be built from source rather than blindly executed.
fwiw deleting the file just results in a build failure and would require extra work, aka = help: message: file missing from serde_derive manifest directory during macro expansion: /tmp/portage/dev-util/maturin-1.3.0/work/cargo_home/gentoo/serde_derive-1.0.183/serde_derive-x86_64-unknown-linux-gnu error: proc-macro derive panicked Not that it'd be impossible to work around but would rather wait for upstream. This should be fixed once it starts using serde >=1.0.184[1] [1] https://github.com/serde-rs/serde/releases/tag/v1.0.184
On a side-note, if concerned, you can keep using maturin-1.1.0 which uses an older serde_derive version which did not do this. Odds are it'll stay in the tree for a while due to stalled stabilizations.
With setuptools-rust, mv ${WORKDIR}/cargo_home/gentoo/serde_derive-1.0.183/src/lib{_from_source,}.rs seems to get part of the way there, but the build fails: error: cannot determine resolution for the macro `Token` --> /var/tmp/portage/dev-util/maturin-1.2.3/work/cargo_home/gentoo/serde_derive-1.0.183/src/bound.rs:292:31 | 292 | colon_token: <Token![:]>::default(), | ^^^^^ | = note: import resolution is stuck, try simplifying macro imports ...
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ea897bcc1f142a3769d42212be884335a153ce1f commit ea897bcc1f142a3769d42212be884335a153ce1f Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2023-12-02 16:12:18 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2023-12-02 16:26:17 +0000 dev-util/maturin: add 1.4.0 Closes: https://bugs.gentoo.org/915176 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> dev-util/maturin/Manifest | 122 ++++++++ dev-util/maturin/maturin-1.4.0.ebuild | 549 ++++++++++++++++++++++++++++++++++ 2 files changed, 671 insertions(+)
