FS#53728 - [blender] symobol lookup error on the current binary package
Attached to Project:
Community Packages
Opened by Dan (drmoose) - Thursday, 20 April 2017, 18:46 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 21 April 2017, 09:32 GMT
Opened by Dan (drmoose) - Thursday, 20 April 2017, 18:46 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 21 April 2017, 09:32 GMT
|
Details
Description:
The current version (17:2.78.c-2) of the blender package has undefined symbols. Someone tried to file a bug for this upstream: https://developer.blender.org/T50581 Additional info: * package version(s): blender-17:2.78.c-2 On my system that brought in the following extra dependencies: alembic-1.7.1-1 blosc-1.11.3-1 jemalloc-4.5.0-1 libspnav-0.2.3-1 log4cplus-1.2.0-3 opencollada-20150702-3 opencolorio-1.0.9-5 openimageio-1.7.13-1 openshadinglanguage-1.7.5-1 opensubdiv-3.1.1-1 openvdb-3.2.0-2 ptex-2.0.62-2 snappy-1.1.4-1 zstd-1.1.4-1 Steps to reproduce: $ pacman -Syyuu $ pacman -S blender --noconfirm $ blender blender: symbol lookup error: blender: undefined symbol: _ZTIN7Alembic3Abc2v97OObjectE Workaround: Downloading the current PKGBUILD and building it unmodified using makepkg results in a working binary. Someone else tried to report this to the blender developers and got shot down because it's not an upstream problem: https://developer.blender.org/T50581 |
This task depends upon
![Link to this comment](../themes/ArchLinux/comment.png)
Aw gee, I really thought a patch version shouldn't break it. How
wrong I was!