Created attachment 912747 [details] build log In file included from python3/pyiptcdata.c:21: python3/pyiptcdata.h:29:10: fatal error: libiptcdata/iptc-data.h: No such file or directory 29 | #include <libiptcdata/iptc-data.h> | ^~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. error: command '/usr/bin/x86_64-pc-linux-gnu-gcc' failed with exit code 1 [31;01m*[0m ERROR: media-libs/libiptcdata-1.0.5-r1::gentoo failed (compile phase): [31;01m*[0m Wheel build failed [31;01m*[0m [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 136: Called src_compile [31;01m*[0m environment, line 4361: Called distutils-r1_src_compile [31;01m*[0m environment, line 2134: Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile' [31;01m*[0m environment, line 834: Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile' [31;01m*[0m environment, line 3976: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' [31;01m*[0m environment, line 3518: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' [31;01m*[0m environment, line 3516: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile' [31;01m*[0m environment, line 1279: Called distutils-r1_run_phase 'distutils-r1_python_compile' [31;01m*[0m environment, line 2116: Called distutils-r1_python_compile [31;01m*[0m environment, line 1938: Called distutils_pep517_install '/var/tmp/portage/media-libs/libiptcdata-1.0.5-r1/work/libiptcdata-1.0.5-python3_12/install' [31;01m*[0m environment, line 2463: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m local wheel=$("${cmd[@]}" 3>&1 1>&2 || die "Wheel build failed"); [31;01m*[0m [31;01m*[0m If you need support, post the output of `emerge --info '=media-libs/libiptcdata-1.0.5-r1::gentoo'`, [31;01m*[0m the complete build log and the output of `emerge -pqv '=media-libs/libiptcdata-1.0.5-r1::gentoo'`. [31;01m*[0m The complete build log is located at '/var/tmp/portage/media-libs/libiptcdata-1.0.5-r1/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/media-libs/libiptcdata-1.0.5-r1/temp/environment'. [31;01m*[0m Working directory: '/var/tmp/portage/media-libs/libiptcdata-1.0.5-r1/work/libiptcdata-1.0.5/python' [31;01m*[0m S: '/var/tmp/portage/media-libs/libiptcdata-1.0.5-r1/work/libiptcdata-1.0.5'
Created attachment 912748 [details] emerge info
Created attachment 912749 [details] emerge pqv
Created attachment 912750 [details] environment info
This blocks building RawTherapee, one of the few raw photo editors.
(tried to reproduce but it built fine here)
It should build with USE=-python, as a workaround.
commit f043a66074d170b289ad0be21ce963236771e1cd Author: Matthew White <mehw.is.me@inventati.org> Date: Sun Oct 13 09:59:53 2024 +0000 media-libs/libiptcdata: add 1.0.5-r2 to fix compiling on Gentoo Fix missing headers and libraries. Compiling from inside the 'python' sub-directory doesn't set ${S} as the top source directory, missing required headers and libraries. [sam: Drop revbump.] Closes: https://bugs.gentoo.org/936589 Closes: https://bugs.gentoo.org/941462 Package-Manager: portage-3.0.65-r1 Signed-off-by: Matthew White <mehw.is.me@inventati.org> Closes: https://github.com/gentoo/gentoo/pull/38974 Signed-off-by: Sam James <sam@gentoo.org>
I don't get it. On one hand, you say it builds fine there, then you suggest an workaround. Why workaround if it builds fine? Would you please provide the same info as I did in order to compare and see what's differet and try to identify the reason it fails here? Thanks.
(In reply to msdobrescu from comment #8) > I don't get it. > On one hand, you say it builds fine there, then you suggest an workaround. > Why workaround if it builds fine? I'm not Greg. I'm just pointing out the obvious workaround in case either you - or someone else - needs it, and also in case Greg had tried with it off.
I apologize for not being precise. Let's read "you" as "you, guys". What I try to say is, on one hand, there is a person saying it builds fine, then another person there is an workaround. So, the workaround means there is a problem to be solved by it, so, for the success story ~ if that is not related to the workaround ~ I need the same build logs and info to be able to track the issue on my system.
(In reply to msdobrescu from comment #10) I'm a different person and I just quickly noted the workaround to help you or anyone else. I haven't attempted to build it and have been working on something else all evening. I also think that even if I were Greg, suggesting a workaround for you would be fine, pending us figuring out the real problem. Anyway, maybe Greg will share his logs (or maybe, as I said, he hadn't tried USE=python, as it's easy to miss this sort of thing).
Sam, I appreciate.
Just as an additional note during my current reinstall, this only seems to be an issue when libiptcdata is not already installed. That is, emerging it once with USE=-python and then doing it again with USE=python seems to work fine. Of course, this suggests it's including the header from the already installed version rather than the version being installed, which is probably not ideal whenever an upgrade comes along.