dev-python/python-zstandard-0.19.0 fails to build in compile phase, with an exception inside an exception. Build log will be attached. Reproducible: Always
Created attachment 850382 [details] build log
Created attachment 850384 [details] emerge --info
Could you upload the bad header? ``` /var/tmp/portage/dev-python/python-zstandard-0.19.0/temp/tmpdk2k2yac.h:1784:16: before: ( ```
Confirm. I have the same error on all 3 machines with Python-3.11.2.
(In reply to Perfect Gentleman from comment #4) > Confirm. I have the same error on all 3 machines with Python-3.11.2. Could you provide the header then?
Reproduced. I assume it's app-arch/zstd-1.5.4 related but I haven't verified that yet.
``` pycparser.plyparser.ParseError: /tmp/portage/dev-python/python-zstandard-0.19.0/temp/tmpxrc2r4yg.h:1784:16: before: ( ``` ``` sudo cat /tmp/portage/dev-python/python-zstandard-0.19.0/temp/tmpxrc2r4yg.h cat: /tmp/portage/dev-python/python-zstandard-0.19.0/temp/tmpxrc2r4yg.h: No such file or directory ``` How can I do it ?
(In reply to Perfect Gentleman from comment #7) > ``` > pycparser.plyparser.ParseError: > /tmp/portage/dev-python/python-zstandard-0.19.0/temp/tmpxrc2r4yg.h:1784:16: > before: ( > ``` No worries, it looks like it deletes the header on error (only just found out). Looking into it now.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=266c564f4074251f35471a300b4986115466b7f1 commit 266c564f4074251f35471a300b4986115466b7f1 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-02-14 04:10:35 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-02-14 04:10:35 +0000 dev-python/python-zstandard: depend on <zstd-1.5.4 Fails to build with newer. Bug: https://bugs.gentoo.org/893948 Signed-off-by: Sam James <sam@gentoo.org> dev-python/python-zstandard/python-zstandard-0.19.0.ebuild | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
dev-python/zstandard was updated to 0.20 and successfully builds with app-arch/zstd-1.5.4-r2. Maybe some tests should be run and bug is up to be closed?
(In reply to ZetaCorvi from comment #10) > dev-python/zstandard was updated to 0.20 and successfully builds with > app-arch/zstd-1.5.4-r2. Maybe some tests should be run and bug is up to be > closed? Yep, thanks!
