Blender 2.53 Beta exits with undefined symbol: gzopen64


#1

I have posted this at blenderartists.org but I’ll leave a copy here, just in case someone here know a way around this:

Blender started and ran well on first run. I did the usual modifications to User Preferences and enabled some of the new add-ons. Then, I closed blender and attempted a restart:

this is what i get from the terminal:

./blender: symbol lookup error: ./blender: undefined symbol: gzopen64

A preliminary investigation points to zlib (I use fedora-13 x86_64). In one forum, someone resolved the problem by getting zlib source from Ubuntu. Turns out there is a modified zlib. I couldn’t find that source. ‘Yum provides gzopen64’ yields nothing.

Funny, I didn’t even enable file compression so I’m wondering why I’m getting the errors. Does anyone know a way around this?, … I really need to experience the cool new stuff inside this Beta release.


#2

hmm, yeah that sounds weird, but I suppose the official linux builder uses ubuntu,
and rather than having built a generic zlib for this might have used the zlib-dev package in ubuntu,
which may wery well be customized for ubuntu, might be why copying the ubuntu version of zlib may help.

try it out, IF you can, otherwise, try reporting a bug, perhaps? :wip:


#3

I got one from Ubuntu repository with no result (same error). I even got the recent version from zlib website (not yet in the fedora repo), compiled it and, eh, … no joy. Someone at blenderartist.org said I have to point blender to the new lib. I don’t know how to do that. It appears to be a known issue anyway … one of the official builders is familiar with it – said “no solution yet”. Those who have worked around the issue are not explaining their procedures illustratively.

Meanwhile, I checked-out a recent blender source with Subversion and compiled it. Its working. I’ll make due with that until there is an official solution.


#4

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.