Blender on Slackware current with kde5 from Alien

dafrasaga · 04-15-2020, 02:10 AM

Hi All,
lately I am in trouble to compile blender..

Quote:

-- Installing: /tmp/SBo/package-blender/usr/share/blender/2.82/datafiles/studiolights/matcap/jade.exr
-- Installing: /tmp/SBo/package-blender/usr/share/blender/2.82/datafiles/studiolights/matcap/check_rim_dark.exr
build/bin/blender: error while loading shared libraries: libGLEW.so.2.1: cannot open shared object file: No such file or directory
executing: build/bin/blender --help
Traceback (most recent call last):
File "./doc/manpage/blender.1.py", line 55, in <module>
blender_help = subprocess.run(
File "/usr/lib64/python3.8/subprocess.py", line 512, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['build/bin/blender', '--help']' returned non-zero exit status 127.

Blender:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.

(Y)es to continue, (N)o to abort, (R)etry the build?:

The compiling is good but when slackbuild tries to install I have that..

Any hints??

PS. I have another pc with the same distro but without kde5 ( normal current) where blender works

gmgf · 04-15-2020, 02:44 AM

Probably blender need glew-2.1, in current, the version is glew-2.2, now.

dafrasaga · 04-15-2020, 03:13 AM

Quote:

Originally Posted by gmgf

Probably blender need glew-2.1, in current, the version is glew-2.2, now.

Hi,
yes .. my distro ( slackware -current has glew-2.2.0 ) but I do not understand why in the other pc all works

gmgf · 04-15-2020, 06:11 AM

Try to rebuild 'openimageio' on this machine, install it, and retry to compil 'blender'

dafrasaga · 04-15-2020, 07:52 AM

Quote:

Originally Posted by gmgf

Try to rebuild 'openimageio' on this machine, install it, and retry to compil 'blender'

Hi, I recompiled openimageio, installed but I have the same error..

Seeing the statement

Quote:

build/bin/blender: error while loading shared libraries: libGLEW.so.2.1: cannot open shared object file: No such file or directory

I checked if blender executable under build/bin directory lacks GLEW2.1..
and with ldd I have

Quote:

root@darkstar:/tmp/SBo/blender-2.82a/build/bin$ ldd blender |grep GLEW
libGLEW.so.2.1 => not found

I tried on the pc where I compiled Blender and that executable doesn't need the libGLEW library (libGLEW.2.2.0 is installed)

Where is the fault??

Regnad Kcin · 04-15-2020, 10:10 AM

Quote:

sbopkg -i blender

The executable file is dumped into /opt/blender/blender

You might have to edit the menu if you don't wish to start it in a terminal.

If you havent used sbopkg before you will want to look at this:
https://github.com/Ponce/slackbuilds...ry-with-sbopkg

and this:
https://sbopkg.org/docs.php

Well that gives you blender-2.78c... not 2.82,
But I was able to get 2.82 up and going
by following the instructions:

Quote:

Linux: Unpack the archive, then run the Blender executable.

dafrasaga · 04-15-2020, 11:34 AM

Quote:

Originally Posted by Regnad Kcin

The executable file is dumped into /opt/blender/blender

You might have to edit the menu if you don't wish to start it in a terminal.

If you havent used sbopkg before you will want to look at this:
https://github.com/Ponce/slackbuilds...ry-with-sbopkg

and this:
https://sbopkg.org/docs.php

Thanks Regnad,
I use sbopkg and the Ponce's current for every out of distro program.. The issue is this one.. I have two PC with the same distro (OK one is with Alien's KDE5 but i think not guilt) and I use sbopkg current on either..

I checked the Cmake Cache.txt file and I have

Quote:

//Path to a library.
GLEW_LIBRARY:FILEPATH=/usr/lib64/libGLEW.so

which in turn is 2.2 and not 2.12 as states the error

Quote:

root@darkstar:/home/gabriele$ ls /usr/lib64/libGLEW* -l
lrwxrwxrwx 1 root root 16 Apr 15 15:26 /usr/lib64/libGLEW.so -> libGLEW.so.2.2.0
lrwxrwxrwx 1 root root 16 Apr 15 15:26 /usr/lib64/libGLEW.so.2.2 -> libGLEW.so.2.2.0
-rwxr-xr-x 1 root root 714736 Apr 4 07:23 /usr/lib64/libGLEW.so.2.2.0

I'm confused

bassmadrigal · 04-15-2020, 11:37 AM

@OP, You may need to uninstall and recompile all the dependencies needed for blender. It's possible one of your previously compiled dependencies was compiled against the older version of glew.

@Regnad Kcin, there are two versions of blender on SBo. One, blender, is a repackaging of the official binary, and the other, Blender, is one that is to be compiled. The repackaged binary is currently untouched on ponce's unofficial repo, but there has been an adjustment of the version to be compiled by adding a flag for boost.

bassmadrigal · 04-15-2020, 11:39 AM

Quote:

Originally Posted by dafrasaga

Thanks Regnad,
I use sbopkg and the Ponce's current for every out of distro program.. The issue is this one.. I have two PC with the same distro (OK one is with Alien's KDE5 but i think not guilt) and I use sbopkg current on either..

I checked the Cmake Cache.txt file and I have

which in turn is 2.2 and not 2.12 as states the error

I'm confused

glew was updated from 2.1 to 2.2 on 5 APR. You might have a package you previously compiled that links against the old glew, and that is probably causing your broken compilation. Once you recompile all the dependencies, it will likely fix your problem.

dafrasaga · 04-15-2020, 11:40 AM

Quote:

Originally Posted by bassmadrigal

@OP, You may need to uninstall and recompile all the dependencies needed for blender. It's possible one of your previously compiled dependencies was compiled against the older version of glew.

I think I did : I re-created the Blender queue and re run all.. You think I have to remove all before rec-create the queue ??

bassmadrigal · 04-15-2020, 11:43 AM

Quote:

Originally Posted by dafrasaga

I think I did : I re-created the Blender queue and re run all.. You think I have to remove all before rec-create the queue ??

Sometimes you need to remove all the packages since they can sometimes have circular dependencies and so they could still link to non-existent software.

dafrasaga · 04-15-2020, 11:45 AM

Quote:

Originally Posted by bassmadrigal

Sometimes you need to remove all the packages since they can sometimes have circular dependencies and so they could still link to non-existent software.

OK.. I'll update you

RadicalDreamer · 04-15-2020, 01:28 PM

Uninstall opencolor and openimage before building those dependencies again. If I remember correctly there is a circular dependency there. The binary Blender package works fine in Slackware. I used the SBo Slackbuild and the 2.82a binary package and installed that way.

Regnad Kcin · 04-15-2020, 02:43 PM

Interesting.
At the end point what is going to be the difference in user functionality between installing the binary direct from the blender site (quick simple easy), the SlackBuild that repackages the binary (has some menu issues), and a compile from scratch capital B Blender (I havent tried it)?

RadicalDreamer · 04-15-2020, 05:14 PM

Quote:

Originally Posted by Regnad Kcin

Interesting.
At the end point what is going to be the difference in user functionality between installing the binary direct from the blender site (quick simple easy), the SlackBuild that repackages the binary (has some menu issues), and a compile from scratch capital B Blender (I havent tried it)?

What menu issues? I don't really dig into the menus except in the viewport. I'm a noob learning retopology at the moment.