Blender tarball no longer finds internal libraries [SOLVED]

[bluenuht]

Forever and a day I have downloaded the latest Blender tarball, currently https://download.blender.org/release/Bl ... x64.tar.xz, extracted in to a folder and ran the binary.

Today I get no error and no GUI, process hangs.

AI has apparently tracked this down to

Code: Select all

readelf -d blender | grep -i rpath
# no output

and

Code: Select all

ldd /usr/bin/blender | grep "not found"
	libblender_cpu_check.so => not found
	libosdGPU.so.3.6.0 => not found
	libosdCPU.so.3.6.0 => not found
	libIex.so.32 => not found
	libOpenEXR.so.32 => not found
	libOpenEXRCore.so.32 => not found
	libIlmThread.so.32 => not found
	libImath.so.30 => not found
	libMaterialXFormat.so.1 => not found
	libMaterialXCore.so.1 => not found
	libembree4.so.4 => not found
	libcycles_kernel_oneapi_aot.so => not found
	libsycl.so.8 => not found
	libOpenColorIO.so.2.4 => not found
	libOpenImageIO.so.3.0 => not found
	libOpenImageIO_Util.so.3.0 => not found
	libOpenImageDenoise.so.2 => not found
	liboslcomp.so.1.14 => not found
	liboslexec.so.1.14 => not found
	liboslquery.so.1.14 => not found
	liboslnoise.so.1.14 => not found
	libusd_ms.so => not found

It has not been able to provide any working solutions and has come up with a number of hilarious hallucinations.

I want to be angry at this, but I would rather just like to know what has happened.

Currently emerge reports

Code: Select all

glibc 2.41-r10
binutils 2.45.1

I also ran ./blender --debug-all and although there was a lot of output there were no obvious errors.

Let me know if there are any diagnostic steps I can take to improve this post.

I am interested in if anyone manually builds Blender from source, my understanding is that the dependencies are many and varied. This is just about the only thing I do not let emerge build from scratch.

[NeddySeagoon]

bluenuht,

Stop. using Artificial Stupidity. As you have discovered, it won't help.
If I download the tarball in your link then do

Code: Select all

tar -tf downloads/blender-5.0.1-linux-x64.tar.xz | less

tar tells me

Code: Select all

blender-5.0.1-linux-x64/
blender-5.0.1-linux-x64/blender-launcher
blender-5.0.1-linux-x64/lib/
blender-5.0.1-linux-x64/lib/libOpenEXRUtil.so.32
blender-5.0.1-linux-x64/lib/libMaterialXRender.so.1
blender-5.0.1-linux-x64/lib/libtbbmalloc.so
blender-5.0.1-linux-x64/lib/libIex.so.32
blender-5.0.1-linux-x64/lib/libMaterialXGenShader.so
blender-5.0.1-linux-x64/lib/libIlmThread.so
blender-5.0.1-linux-x64/lib/libusd_ms.so
blender-5.0.1-linux-x64/lib/libOpenImageDenoise.so
blender-5.0.1-linux-x64/lib/libOpenEXR.so.32
blender-5.0.1-linux-x64/lib/libOpenImageDenoise_device_cuda.so.2.3.3
blender-5.0.1-linux-x64/lib/libtbbmalloc.so.2.13
blender-5.0.1-linux-x64/lib/libIlmThread.so.32
blender-5.0.1-linux-x64/lib/libMaterialXCore.so.1
blender-5.0.1-linux-x64/lib/libOpenEXRCore.so.32.3.3.5
blender-5.0.1-linux-x64/lib/libMaterialXFormat.so
blender-5.0.1-linux-x64/lib/libOpenEXR.so.32.3.3.5
blender-5.0.1-linux-x64/lib/libtbb.so.12
blender-5.0.1-linux-x64/lib/libMaterialXGenOsl.so
blender-5.0.1-linux-x64/lib/libosdGPU.so
blender-5.0.1-linux-x64/lib/libOpenImageIO.so

so at least some of the libraries are there.

What does /usr/bin/blender do on your system?
When you untar that binary, it will create a ./blender-5.0.1-linux-x64/ directory wherever you untar it to.
That will not be in your $PATH, so its contents won't be found.

/usr/bin is managed by portage. Its a verybadthing to install things not managed by portage there.
Binaries should normally go to /opt or possibly /usr/local

Try

Code: Select all

$PATH
bash: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/lib/llvm/21/bin:/usr/lib/llvm/20/bin:/usr/lib64/subversion/bin:/usr/lib64/opencascade/bin
:/usr/portage/local/layman/sunrise/scripts:/usr/portage/local/layman/sunrise/scripts: No such file or directory

bash displays your $PATH setting followed by an error. That's expected.

Oh, Layman has been gone for a long time, so I have some junk in my $PATH

Code: Select all

blender-5.0.1-linux-x64/blender-launcher

I wonder what blender-launcher does?

[Hu]

Try

Code: Select all

$PATH
bash: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/lib/llvm/21/bin:/usr/lib/llvm/20/bin:/usr/lib64/subversion/bin:
/usr/lib64/opencascade/bin:/usr/portage/local/layman/sunrise/scripts:/usr/portage/local/layman/sunrise/scripts: No such file or directory

bash displays your $PATH setting followed by an error. That's expected.

Using declare -p PATH (note the lack of $) will show the path in a reusable form, without an error message. Unlike echo $PATH, the result of declare -p PATH is supposed to be unambiguous, even in the presence of weird characters in the variable.

[bluenuht]

blender-launcher works!!

thanks, I had never noticed that blender-launcher script before, I always soft linked /usr/bin/blender to the blender executable in my ~/src/blender-{version} folder

It does not get to the core of the issue but I am marking the thread [SOLVED] as I can now run blender again.

To reiterate:

1. Extracting blender tarball to into its own folder and running it has worked for years (for me)
2. Nothing changed in the previously working blender extracted folder
3. updated Gentoo
4. blender fails with no errors

Personally, I love errors, Linux errors are normally highly detailed and descriptive.

Would still like to know what actually changed when I updated Gentoo that could have caused all this. I generally update Gentoo 2-3 times a week.

Not to mention I really do not understand what the underlying cause is. It does seem that based on the blender-launcher script that it is something to do with the precedence of library loading.