Bug 29726 - dnf build-dep does not install all required deps to build Blender from source
Summary: dnf build-dep does not install all required deps to build Blender from source
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-04 15:19 CET by Kristoffer Grundström
Modified: 2022-07-03 23:05 CEST (History)
4 users (show)

See Also:
Source RPM: dnf-4.6.0-1.mga8.src.rpm
CVE:
Status comment:


Attachments
CMakeError output (1.27 KB, text/plain)
2021-12-04 15:43 CET, Kristoffer Grundström
Details
dnf builddep output (74.52 KB, text/plain)
2021-12-14 21:34 CET, Neal Gompa
Details

Description Kristoffer Grundström 2021-12-04 15:19:57 CET
Description of problem: I cloned the Blender source code and used sudo dnf build-dep blender to install all the required packages to build Blender as it has been released as version 3.0. However when I ran make to build it it failed with this error:

[kristoffer@ip249-2-1 blender]$ make

Configuring Blender in "/home/kristoffer/Desktop/build_linux" ...
CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:218 (message):
  Could NOT find PythonLibsUnix (missing: PYTHON_LIBRARY PYTHON_LIBPATH
  PYTHON_INCLUDE_DIR PYTHON_INCLUDE_CONFIG_DIR)
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:582 (_FPHSA_FAILURE_MESSAGE)
  build_files/cmake/Modules/FindPythonLibsUnix.cmake:176 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  build_files/cmake/platform/platform_unix.cmake:113 (find_package)
  CMakeLists.txt:982 (include)


-- Configuring incomplete, errors occurred!
See also "/home/kristoffer/Desktop/build_linux/CMakeFiles/CMakeOutput.log".
See also "/home/kristoffer/Desktop/build_linux/CMakeFiles/CMakeError.log".
make: *** [GNUmakefile:344: all] Error 1

Version-Release number of selected component (if applicable): 4.6.0

How reproducible: All the time.

Steps to Reproduce:
1. Open a terminal window.
2. Login as root OR by using sudo (make sure that your user is a part of the wheel user group) followed by executing dnf build-dep blender -y
3. Clone the Blender source code.
4. Enter the main directory for the source code.
5. Run make.
6. See the error mentioned above.
Comment 1 Kristoffer Grundström 2021-12-04 15:43:08 CET
Created attachment 13018 [details]
CMakeError output

CC: (none) => lovaren

Comment 2 Lewis Smith 2021-12-05 19:41:09 CET
Usually when you raise a bug like this, it turns out that you are doing something not quite right. I cannot judge this case, so am leaving it with BugSquad for wider visibility. CC'ing Neal for DNF, although it is often tmb who explains things.

Source RPM: dnf => dnf-4.6.0-1.mga8.src.rpm
CC: (none) => lewyssmith, ngompa13

Comment 3 Neal Gompa 2021-12-14 21:34:59 CET
Created attachment 13052 [details]
dnf builddep output

So aside from a missing build dependency in the spec on "make" (which I had to install separately after using "dnf builddep"), it looks like everything is there.

I see lib64python3-devel installed, which provides all the things the Blender CMakeLists should be able to detect and use for building Blender.

However, it doesn't work because the Blender CMake scripts are looking for Python 3.9 or higher (Mageia 8 only has Python 3.8), and when I try to force it, it fails saying it needs Python 3.9.

For example:

[root@aef0fecb929c blender-3.0.0]# cmake -B ../blender-build -S . -DPYTHON_VERSION=3.8 -DWITH_PYTHON_INSTALL=OFF -DWITH_PYTHON_INSTALL_REQUESTS=OFF
-- WITH_DRACO requires WITH_PYTHON_INSTALL to be ON, disabling WITH_DRACO for now
CMake Error at CMakeLists.txt:881 (message):
  At least Python 3.9 is required to build, but found Python 3.8


-- Configuring incomplete, errors occurred!
See also "/blender-build/CMakeFiles/CMakeOutput.log".
See also "/blender-build/CMakeFiles/CMakeError.log".
Comment 4 Marja Van Waes 2022-07-03 23:05:55 CEST
Thanks for having looked into this, Neal.

Closing as invalid

CC: (none) => marja11
Resolution: (none) => INVALID
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.