Page 1 of 2

Blender 2.33 is here !!!

Posted: Sat May 01, 2004 2:41 pm
by psergiu
Get your Blender 2.33 from:
http://www.blender3d.org/cms/Blender.31.0.html
... and Yafray render engine:
http://download.blender.org/release/yafray.0.0.6/

Release-info:
http://www.blender3d.org/cms/Blender_2_33.66.0.html

The Game Engine is back !!!

Re: Blender 2.33 is here !!!

Posted: Mon May 03, 2004 7:47 pm
by GeneratriX
psergiu wrote:Get your Blender 2.33 from:
http://www.blender3d.org/cms/Blender.31.0.html
... and Yafray render engine:
http://download.blender.org/release/yafray.0.0.6/

Release-info:
http://www.blender3d.org/cms/Blender_2_33.66.0.html

The Game Engine is back !!!


Very cool!

Very good with IRIX >6.5.20...
but don't get resolved a few symbols under IRIX 6.5.17...

Posted: Sat Jul 10, 2004 4:42 pm
by GIJoe
just wanted to try it out again after some years and i get "rld: Fatal error: attempted access to unresolvable symbol in ./blender: _xpg5_vsnprintf"

how to make it work?

edit: blender 2.33 on 6.5.12

Posted: Sat Jul 10, 2004 4:56 pm
by NauSeuM
sounds like you'll have to upgrade your Irix.

Posted: Sun Jul 11, 2004 5:18 am
by GIJoe
maybe, but it isn't worth it for just having a look. will get windows binary instead.

Posted: Sun Jul 11, 2004 6:26 am
by NauSeuM
well, i would disagree mostly because there is a lot of recent software 6.5.12 will have issues with..

but to each...

Posted: Sun Jul 11, 2004 12:49 pm
by GIJoe
well, all the software i acquired the machine for runs without flaws. in my experience a lot of freeware causes troubles though. that's why i try to stay away from that as much as i can.

Posted: Sun Jul 11, 2004 1:54 pm
by nekonoko
As Diego mentioned above, the new version requires IRIX 6.5.17+

Posted: Thu Jul 15, 2004 1:35 pm
by ChiaHos
GIJoe wrote:just wanted to try it out again after some years and i get "rld: Fatal error: attempted access to unresolvable symbol in ./blender: _xpg5_vsnprintf"

how to make it work?

edit: blender 2.33 on 6.5.12


That missing symbol problem was a result of the move to Python 2.3.
The configure script in Python 2.3 looks for that symbol in libc, which
it finds in Irix >= 6.5.20, and the dependency gets compiled in.

I've built a version of python that doesn't depend on that symbol
and compiled recent cvs with it. You might want to test if it
works on your system (also try out some of the latest features
-- new unwrapper, creased subsurfs, etc -- to ensure they run on Irix):

http://bebop.cns.ualberta.ca/~cwant/ble ... ips.tar.gz

You may wish to report any problems you find to the blender
bug tracker (be sure to specify that the problem is with recent cvs,
and include as much information about your system as possible):

http://projects.blender.org/tracker/?at ... unc=browse

Regards,
Chris

Posted: Wed Jul 21, 2004 2:26 pm
by nekonoko
Fantastic, I'll give the CVS version a try this weekend!

Posted: Wed Jul 21, 2004 6:04 pm
by skywriter
http://bebop.cns.ualberta.ca/~cwant/ble ... ips.tar.gz

this is good. it even runs on 6.5.15. are the lib/iris-6.5.mips files fixed then?
it would be nice to know how the new features worked without having to dredge through the blender.org forum drek. any new feature documentation available?

Posted: Thu Jul 22, 2004 10:42 am
by ChiaHos
skywriter wrote:this is good. it even runs on 6.5.15. are the lib/iris-6.5.mips files fixed then?


Not yet ... I had hoped to get some feedback about whether the binary
was usable first before committing the modified python libs. Will commit soon.

Unfortunately we've hit another snag: The current CVS compiles the
solid/qhull collision detection libs, which seems to only want to
compile with MipsPro 7.4 (unless somebody knows how to process
lines like "#include <cmath>" wth MipsPro 7.3.1.3m?).

Here is a cvs compile from today that was compiled with the 7.4 compiler
if anybody would like to test it:

http://bebop.cns.ualberta.ca/~cwant/ble ... ips.tar.gz

(MipsPro 7.4 will probably be the compiler used to produce the 2.34 binary that
is expected out in a couple of weeks.)

BTW: how does our old friend 'sequence.blend' fare with that binary?

skywriter wrote:it would be nice to know how the new features worked without having to dredge through the blender.org forum drek. any new feature documentation available?


There are some preliminary docs about the latest changes/features here:

http://www.blender3d.org/cms/Changes_si ... 319.0.html

Chris

Posted: Thu Jul 22, 2004 10:58 am
by skywriter
ChiaHos wrote:BTW: how does our old friend 'sequence.blend' fare with that binary?


I doubt it's a problem anymore. I'm pretty certain the problem stemmed from a mismatch between 7.3.1.3m development components, and 6.5.21's partial upgrade of those systems, and the state of the precompiled blender libs. I never had time to sort it out (or do anything else for that matter). I've upped to 6.5.23 (the EOL for indy/indigo2) and will be sorting out my 7.4 compile platform. all takes time.

the unfortunate side effect of having more than one machine is you have to maintain them all as well.

Posted: Thu Jul 22, 2004 3:01 pm
by dexter1
ChiaHos wrote:Unfortunately we've hit another snag: The current CVS compiles the solid/qhull collision detection libs, which seems to only want to compile with MipsPro 7.4 (unless somebody knows how to process lines like "#include <cmath>" wth MipsPro 7.3.1.3m?).


This has been covered in an old thread about Octave builds on IRIX:
viewtopic.php?t=710

The trick is to get separate CC-isoheaders to augment your MIPSPro 7.3.1.3m. There are also patches from SGI about this, but are behind support contracts. :( Unfortunately the tarball mentioned in the above thread is gone, but, i found an Octave reference:
http://wiki.octave.org/wiki.pl?PaulKienzleIrixConf

And here is the CC-isoheaders link:
http://octave.sourceforge.net/MIPS73-isoheaders.tar.gz

Posted: Fri Jul 23, 2004 8:17 am
by ChiaHos
dexter1 wrote:The trick is to get separate CC-isoheaders to augment your MIPSPro 7.3.1.3m. There are also patches from SGI about this, but are behind support contracts. :( Unfortunately the tarball mentioned in the above thread is gone, but, i found an Octave reference:
http://wiki.octave.org/wiki.pl?PaulKienzleIrixConf


Thanks for the great tip!

Ideally I'd like to find a source level solution that
could be sent upstream to the solid library author,
i.e., some thing like

#ifdef GOT_ISOHEADERS
#include <cmath>
#else
/* do something else here */
#endif

Unfortunately my C++ knowledge is novice at best,
but my guess is that the source is probably too
dependent on the new-fangled C++ stuff for such a
solution to exist.

There is one last workaround that would allow 7.3.1.3m
compatibility: blender has a cvs module of pre-compiled
libs, so the solid stuff could be compiled with 7.4
and committed to that module, with the build system
altered to use that lib under irix rather than trying to compile
the library itself (this was the behavior of the build system
up until about a week ago, but the gameengine
maintainer wants to move away from this practice).

Chris