Rocky Linux 9 build #114
Replies: 15 comments 9 replies
-
|
Also, thanks to @panda1100 for the work on building on Rocky 9 in apptainer! |
Beta Was this translation helpful? Give feedback.
-
|
@rgwilson68 I tested building MoonRay without
with Apptainer, yes |
Beta Was this translation helpful? Give feedback.
-
|
Yes, Arras now has a stub version of cgroup that it uses if libcgroup can't be found. You can just remove the line that tries to fetch libcgroup from kojihub if it is no longer there. If cgroups are available, the Arras node can use them to restrict resources used by rendering. However, this functionality is disabled by default, and compiling without libcgroup should be fine for most people. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, My graphics cards have a dev rating of 5 which is too low I know but does this explain the black? Here are some of the errors I'm getting if I go with the build command on the Rocky9 page it stalls at around 86% with a complaint about opencolorio.... gmake[3]: *** [Makefile:146: all] Error 2 But if I try the command from the main install instructions page targetting Rocky9 it works 100% ( but everything renders black ) Some of the errors I've gotten along the way... Error: RdlInstancerGeometry("/scene/objects/"): Did not find any references geometry. Please make sure the "referencess" field contains at least one source references geometry and specifically for the old cards... I'm guessing this will work better when I upgrade the cards. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Have you checked NVIDIA driver version and CUDA toolkit version compatibility. I'm guessing driver on your system too old. Just a hunch though. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Panda, Thanks for the tip. I reinstalled Rocky9 from scratch and installed the nvidia drivers properly ( not a straightforward matter ). --2024-01-12 16:24:56-- https://kojihub.stream.centos.org/kojifiles/packages/libcgroup/0.42.2/5.el9/x86_64/libcgroup-0.42.2-5.el9.x86_64.rpm --2024-01-12 16:25:01-- https://kojihub.stream.centos.org/kojifiles/packages/libcgroup/0.42.2/5.el9/x86_64/libcgroup-devel-0.42.2-5.el9.x86_64.rpm Is that enough to throw everything off? What would you recommend? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
I'm kinda new at this...the driver version is... IS that too old? I got some new errors too... /bin/ld: CMakeFiles/ociolutimage.dir/main.cpp.o: undefined reference to symbol '_ZN16OpenImageIO_v2_310ParamValue11clear_valueEv' The thing is - I was able to build this before Xmas on this machine without Rocky9 support. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Those two files is not available anymore. comment out those two just works.
|
Beta Was this translation helpful? Give feedback.
-
|
@mpjohn I recommend you to check this official document about compatibility https://docs.nvidia.com/deploy/cuda-compatibility/ |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your help panda1100. I'm going to update the cards tomorrow. This might be a silly question but do I need to rebuild Moonray once I update the hardware? I'm hoping no. Also I'm a bit disappointed that Moonray wasn't able to command line render with the older cards in place. Is that expected behavour? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Also...I got these extra errors when I built everything from scratch... ( a ) should I be concerned? ( b ) does it explain black renders? -- * Checking for dependencies... -- Could NOT find Imath (missing: Imath_DIR) CMake Warning (dev) at /installs/cmake-3.23.1-linux-x86_64/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:438 (message): -- Could NOT find JPEG (missing: JPEG_LIBRARIES JPEG_INCLUDE_DIRS) -- Could NOT find Ptex (missing: Ptex_DIR) Make Warning at src/heif.imageio/CMakeLists.txt:11 (message): CMake Warning at src/jpeg2000.imageio/CMakeLists.txt:11 (message): CMake Warning at src/raw.imageio/CMakeLists.txt:11 (message): |
Beta Was this translation helpful? Give feedback.
-
|
OK. I've updated to an RTX4000 card which should work and while the warning signs are gone everything apart from the test rectangle is still rendering black. |
Beta Was this translation helpful? Give feedback.
-
|
I'm stumped!! Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Here's my debug file which suggests that the geometry is being loaded. Any advice on how to get this thing working would be greatly [appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
Ah! I see the issue in the first line of your debug_output.txt file: It's how you are running the moonray command. These example scenes are split into two files: scene.rdla and scene.rdlb The scene.rdlb file is binary and contains the remaining array attributes -- things such as vertex data, normals, texture coordinates, etc. When you run moonray (or moonray_gui) you must pass them both in on the command-line, for example: You can read more about the RDL2 format here: Let us know how this works for you!
|
Beta Was this translation helpful? Give feedback.
-
|
That's perfect. I feel pretty stupid but hopefully someone out there can learn from my mistake! |
Beta Was this translation helpful? Give feedback.
-
|
Please don't feel bad! Congrats on getting it built and running (not an easy task!). I think we could do a better job of documenting this. I think it is fair to say that this is not going to be obvious to a new moonray user. I'll look for ways to improve our documentation on rendering these example scenes. These scenes could have been entirely contained in a single RDLA file (long, but human readable), or in a single RDLB file (faster to load, smaller on disk), or split into both ascii/binary formats as I chose to do. We developers sometimes work with the scene split this way for convenience when hand-editing the files during testing, and it didn't occur to me that it might be confusing to distribute them this way. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Jon. It's great to have it up and running!!
…On Thu, Jan 18, 2024 at 5:19 PM Jon Lanz ***@***.***> wrote:
Please don't feel bad! Congrats on getting it built and running (not an
easy task!).
I think we could do a better job of documenting this. I think it is fair
to say that this is not going to be obvious to a new moonray user. I'll
look for ways to improve our documentation on rendering these example
scenes.
These scenes could have been entirely contained in a single RDLA file
(long, but human readable), or in a single RDLB file (faster to load,
smaller on disk), or split into both ascii/binary formats as I chose to do.
We developers sometimes work with the scene split this way for convenience
when hand-editing the files during testing, and it didn't occur to me that
it might be confusing to distribute them this way.
—
Reply to this email directly, view it on GitHub
<#114 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANSSPIS6O63FII7CYWHBZCLYPFKSTAVCNFSM6AAAAAA24BA3HOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCNZSGEYDC>
.
You are receiving this because you were mentioned.Message ID:
<dreamworksanimation/openmoonray/repo-discussions/114/comments/8172101@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I've been doing some more testing and found the following errors... Is this an opencolorIO issue? Does anyone know how to solve it?
|
Beta Was this translation helpful? Give feedback.
-
|
Maybe I should mention that since building Moonray I have installed Maya and Houdini - I've also attempted a few times to build Moonray against Houdini. Could any of this have messed up my original install of Moonray? |
Beta Was this translation helpful? Give feedback.
-
|
Possibly. Maya and Houdini might have different library versions, might have put a conflicting symlink somewhere, etc. |
Beta Was this translation helpful? Give feedback.
-
|
Is CentOS just going to be easier to set up than Rocky Linux? |
Beta Was this translation helpful? Give feedback.
-
|
Hi There,
I've built Moonray against the Houdini libraries as described on the forums.
Surprisingly this worked without any issues...( at all! )
So now I can go into Solaris and turn on Moonray.
If the scene has nothing in it then hydra works fine and I can see feedback
in the terminal.
Now if I make a component builder. Add GEO. Then add a Dwa base material
and a collector.
It crashes every time.
Any ideas what might be happening?
Thanks
Matt
|
Beta Was this translation helpful? Give feedback.
-
|
I notice that the rocky 9 install_packages.sh still have a few redundant lines... wget https://kojihub.stream.centos.org/kojifiles/packages/libcgroup/0.42.2/5.el9/x86_64/libcgroup-0.42.2-5.el9.x86_64.rpm ...which if I'm not mistaken will cause a 404 error. It might be worth editing this for the next version? |
Beta Was this translation helpful? Give feedback.
-
The source code has been updated in 1.3.0.0 to build with GCC version 11 and Qt 5.15.3, making it buildable in Rocky Linux 9.
There is an initial set of build instructions and scripts in /building/Rocky9 (openmoonray repo).
The Centos 7 build instructions are unchanged in this release, but the plan is to make some changes in line with the new Rocky 9 and move them to a Centos7 subdirectory, together with some more in-depth build documentation. This should be ready for the next release.
Note that there are dependency version updates in this release (see the release notes for details).
A couple of build FAQs in the meantime:
Can you build MoonRay without root permissions?
In theory, yes, but the difficult part is installing the packages we get from the Linux distribution. Installing with the yum/dnf package managers generally requires root access. They do have options to set an alternate install location, but the general opinion seems to be that it is difficult to get everything to work correctly if you do this. The dependencies built from source can be installed anywhere by editing the CMakeFiles.txt and presets files : this will get simpler in the next release. MoonRay itself can be installed anywhere, using the --prefix option to cmake --install.
Do you have to use git submodules and clone the repositories in a fixed directory structure?
No, but it is recommended for most users. Each of the 18 source repositories can be cloned wherever you want and built separately using CMake -- this is how we build them at DreamWorks Animation. However, this requires building them in the correct order and configuring the CMake build of each repository to be able find the installed result of the other repositories it depends on. We use Rez 2 and the rez-build command to do this (that is what the "package.py" file in each repository is for).
We created the "openmoonray" repository to provide a way of cloning and building everything together as one CMake project, but if you have a preexisting system for managing packages and package dependencies you should be able to use that instead.
Beta Was this translation helpful? Give feedback.
All reactions