https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: media-gfx/blender-2.83.15 fails to compile. Discovered on: amd64 (internal ref: ci) NOTE: This machine uses GCC-11: https://gcc.gnu.org/gcc-11/porting_to.html If you think this is a GCC-11 related issue, please block bug 732706.
Created attachment 715023 [details] build.log build log and emerge --info
Created attachment 715026 [details] 1-CMakeError.log 1-CMakeError.log
Created attachment 715029 [details] 1-CMakeOutput.log 1-CMakeOutput.log
Possible context of error(s): -- Could NOT find OpenImageDenoise (missing: OPENIMAGEDENOISE_LIBRARY OPENIMAGEDENOISE_INCLUDE_DIR) -- Could NOT find XR_OPENXR_SDK (missing: XR_OPENXR_SDK_LOADER_LIBRARY XR_OPENXR_SDK_INCLUDE_DIR)
The actual fatal error curing configure is: WITH_MOD_OCEANSIM requires WITH_FFTW3 to be ON The ebuilds have WITH_MOD_OCEANSIM unconditionally enabled, but WITH_FFTW3 is controlled by the fftw use flag. This impacts both 2.83 and 2.93.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=17e6b76d90cf813b637139461adb5bc715c240b6 commit 17e6b76d90cf813b637139461adb5bc715c240b6 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-06-12 07:18:44 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-06-12 07:19:05 +0000 media-gfx/blender: make oceansim dependent on FFTW Bug: https://bugs.gentoo.org/795159 Signed-off-by: Sam James <sam@gentoo.org> media-gfx/blender/blender-2.83.15.ebuild | 2 +- media-gfx/blender/blender-2.93.0.ebuild | 2 +- media-gfx/blender/blender-9999.ebuild | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
(In reply to Matthew Turnbull from comment #5) > The actual fatal error curing configure is: > > WITH_MOD_OCEANSIM requires WITH_FFTW3 to be ON > > The ebuilds have WITH_MOD_OCEANSIM unconditionally enabled, but WITH_FFTW3 > is controlled by the fftw use flag. > > This impacts both 2.83 and 2.93. Thanks. Keeping open for DarkDefender to comment on if we want to make FFTW always on or...?
Also, it would appear that Blender 2.83 is NOT (currently) Python 3.9 compatible. /tmp/portage/media-gfx/blender-2.83.15/work/blender-2.83.15/source/blender/python/mathutils/mathutils_Vector.c:379:30: error: ‘PyNoArgsFunction’ undeclared (first use in this function); did you mean ‘PyCFunction’? https://developer.blender.org/T78089
(In reply to Matthew Turnbull from comment #8) > Also, it would appear that Blender 2.83 is NOT (currently) Python 3.9 > compatible. > > /tmp/portage/media-gfx/blender-2.83.15/work/blender-2.83.15/source/blender/ > python/mathutils/mathutils_Vector.c:379:30: error: ‘PyNoArgsFunction’ > undeclared (first use in this function); did you mean ‘PyCFunction’? > > https://developer.blender.org/T78089 I suppose we could backport it but I don't see the point. Dropping.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c476c026e6bc99ad755322fb974e83a3155bd62f commit c476c026e6bc99ad755322fb974e83a3155bd62f Author: Sam James <sam@gentoo.org> AuthorDate: 2021-06-12 07:34:53 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-06-12 07:34:53 +0000 media-gfx/blender: drop support for Python 3.9 in 2.83.15; use newest slot Bug: https://bugs.gentoo.org/795159 Signed-off-by: Sam James <sam@gentoo.org> media-gfx/blender/blender-2.83.15.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
> Thanks. Keeping open for DarkDefender to comment on if we want to make FFTW always on or...? I think we'll just make fftw a hard requirement. I don't see any reason to have it be optional except just making the ebuild more complicated. There are not really any upsides with using Blender without FFTW support (besides not having to install the lib)
Aha, I see you already changed it. Then we can keep it as is.
Yeah , As I saw , It seems like an updated format. https://bit.ly/3BQjleg
