installing psycho 1.6 on Mavericks

[boblishman]

Can Age building be done on a Mac running Mavericks??

When I try and install psyco it throws up all kind of errors and reading up it seems it won't install on 64 bit. TBH, I'm totally confused. I have managed to get a textureless Age to export but as soon as I add a texture, PyPrp halts when it tries to process the texture, complaining that it

Code: Select all

Checking for installed Python... got it!
Psyco not available to PyPRP...

and then when trying to convert the texture ...

Code: Select all

Imagename:GreenGrass(512x512).j
Resize Image: True
Make MipMaps: True
Calculate Alpha:False
MipMap Gauss:False
Mipmap AlphaMult:1.0
CompressionType: DXT
 SubType: DXT5
---------------

     Converting texture GreenGrass(512x512).j...
      Image size: 512x512
      DXT Compressing texture .... this can take a few minutes
     Compressing DXT5
     MipMapping....
      Level 0 512x512
      Level 1 256x256
Traceback (most recent call last):
  File "/Users/boblishman/Documents/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_Export.py", line 174, in open_file
    export_age(agename,basepath,selection,merge)
  File "/Users/boblishman/Documents/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_Export.py", line 88, in export_age
    page.export_all(selection)
  File "/Users/boblishman/Desktop/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_ResManager.py", line 792, in export_all
  File "/Users/boblishman/Desktop/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_DrawClasses.py", line 1576, in _Export
  File "/Users/boblishman/Desktop/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_DrawClasses.py", line 1801, in export_obj
  File "/Users/boblishman/Desktop/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_MatClasses.py", line 547, in export_mat
  File "/Users/boblishman/Desktop/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_MatClasses.py", line 420, in FromBlenderMat
  File "/Users/boblishman/Desktop/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_MatClasses.py", line 835, in FromBlenderMTex
  File "/Users/boblishman/Desktop/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_MatClasses.py", line 2177, in _Export
  File "/Users/boblishman/Desktop/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_MatClasses.py", line 2009, in FromBlenderImage
  File "/Users/boblishman/Desktop/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_MatClasses.py", line 2117, in FromRawImage
  File "/Users/boblishman/Desktop/blender-2.49b-OSX-10.5-py2.5-intel/blender.app/Contents/MacOS/.blender/scripts/PyPRP/prp_DXTConv.py", line 75, in resize_alphamult
  File "/Library/Python/2.5/site-packages/PIL/Image.py", line 1763, in new
    return Image()._new(core.fill(mode, size, color))
SystemError: new style getargs format but argument is not a tuple

When I try to install the Psycho 1.6 it just fails and I get:

Code: Select all

Bobs-iMac:psyco-1.6 19.48.55 boblishman$ python setup.py install
PROCESSOR = 'ivm'
running install
running build
running build_py
running build_ext
building 'psyco._psyco' extension
cc -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386 -g -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -DENABLE_DTRACE -DMACOSX -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -fwrapv -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch i386 -pipe -DALL_STATIC=1 -Ic/ivm -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c c/psyco.c -o build/temp.macosx-10.9-intel-2.7/c/psyco.o
In file included from c/psyco.c:3:
In file included from c/codemanager.h:10:
In file included from c/dispatcher.h:12:
c/codegen.h:15:3: error:
      "-----------------------------------------------------"
# error "-----------------------------------------------------"
  ^
c/codegen.h:16:3: error:
      "Sorry, non-32-bit platforms are not supported at all."
# error "Sorry, non-32-bit platforms are not supported at all."
  ^
c/codegen.h:17:3: error:
      "You may try with a Python compiled in 32-bit         "
# error "You may try with a Python compiled in 32-bit         "
  ^
c/codegen.h:18:3: error:
      "compatibility mode.  Note that Psyco will probably   "
# error "compatibility mode.  Note that Psyco will probably   "
  ^
c/codegen.h:19:3: error:
      "never support non-32-bit platforms, as it is no      "
# error "never support non-32-bit platforms, as it is no      "
  ^
c/codegen.h:20:3: error:
      "longer actively developed.  Instead, the PyPy group  "
# error "longer actively developed.  Instead, the PyPy group  "
  ^
c/codegen.h:21:3: error:
      "plans to replace it with a more flexible and easily  "
# error "plans to replace it with a more flexible and easily  "
  ^
c/codegen.h:22:3: error:
      "retargettable Psyco-for-PyPy during the year 2006.   "
# error "retargettable Psyco-for-PyPy during the year 2006.   "
  ^
c/codegen.h:23:3: error:
      "See http://codespeak.net/pypy/                       "
# error "See http://codespeak.net/pypy/                       "
  ^
c/codegen.h:24:3: error:
      "-----------------------------------------------------"
# error "-----------------------------------------------------"
  ^
In file included from c/psyco.c:4:
In file included from c/stats.h:14:
In file included from c/Python/frames.h:11:
c/ivm/idispatcher.h:114:29: warning: implicit conversion loses integer
      precision: 'long' to 'int' [-Wshorten-64-to-32]
        int distance = code - po->code;
            ~~~~~~~~   ~~~~~^~~~~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:42:
In file included from c/ivm/iinitialize.h:11:
In file included from c/ivm/iprocessor.c:294:
c/ivm/prolog/insns-threaded.i:673:7: warning: explicitly assigning a variable of
      type 'word_t' (aka 'long') to itself [-Wself-assign]
accum = accum;
~~~~~ ^ ~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:42:
In file included from c/ivm/iinitialize.h:12:
In file included from c/ivm/idispatcher.c:4:
c/ivm/ipyencoding.h:16:24: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
        int index        = ep - dict->ma_table;
            ~~~~~          ~~~^~~~~~~~~~~~~~~~
c/ivm/ipyencoding.h:44:21: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
        int index = new_ep - dict->ma_table;
            ~~~~~   ~~~~~~~^~~~~~~~~~~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:42:
In file included from c/ivm/iinitialize.h:12:
c/ivm/idispatcher.c:43:23: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
      codesize = code - dm->code_origin;
               ~ ~~~~~^~~~~~~~~~~~~~~~~
c/ivm/idispatcher.c:139:32: warning: implicit conversion loses integer
      precision: 'long' to 'int' [-Wshorten-64-to-32]
      a->source = RunTime_New1(dststack, false, false);
                  ~~~~~~~~~~~~ ^~~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:46:
c/dispatcher.c:130:35: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
  int opc_size = current->buf_end - current->buf_opc;
      ~~~~~~~~   ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
c/dispatcher.c:143:38: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
  int opc_size = cmpinternal.buf_end - cmpinternal.buf_opc;
      ~~~~~~~~   ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
c/dispatcher.c:144:56: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
  int arg_size = ((signed char*) cmpinternal.buf_args) - cmpinternal.buf_begin;
      ~~~~~~~~   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~
c/dispatcher.c:145:65: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
  int nsize = (cmpinternal.buf_end - cmpinternal.buf_begin) * 3 / 2;
      ~~~~~   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
c/dispatcher.c:239:18: warning: cast to 'vinfo_t *' (aka 'struct vinfo_s *')
      from smaller integer type 'int' [-Wint-to-pointer-cast]
        a->tmp = (vinfo_t*) (++cmpinternal.tmp_counter);
                 ^
c/dispatcher.c:405:34: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
  opc_size = cmpinternal.buf_end - cmpinternal.buf_opc;
           ~ ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
c/dispatcher.c:406:52: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
  arg_size = ((signed char*) cmpinternal.buf_args) - cmpinternal.buf_begin;
           ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~
c/dispatcher.c:1408:11: warning: implicit conversion loses integer precision:
      'Py_ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
  limit = PyList_GET_SIZE(plist);
        ~ ^~~~~~~~~~~~~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/listobject.h:63:32: note:
      expanded from macro 'PyList_GET_SIZE'
#define PyList_GET_SIZE(op)    Py_SIZE(op)
                               ^~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/object.h:116:56: note:
      expanded from macro 'Py_SIZE'
#define Py_SIZE(ob)             (((PyVarObject*)(ob))->ob_size)
                                 ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:46:
c/dispatcher.c:1416:13: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
      num = PyInt_AS_LONG(o1);
          ~ ^~~~~~~~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/intobject.h:52:51: note:
      expanded from macro 'PyInt_AS_LONG'
#define PyInt_AS_LONG(op) (((PyIntObject *)(op))->ob_ival)
                           ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:46:
c/dispatcher.c:1437:7: warning: implicit conversion loses integer precision:
      'Py_ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
  i = PyList_GET_SIZE(plist);
    ~ ^~~~~~~~~~~~~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/listobject.h:63:32: note:
      expanded from macro 'PyList_GET_SIZE'
#define PyList_GET_SIZE(op)    Py_SIZE(op)
                               ^~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/object.h:116:56: note:
      expanded from macro 'Py_SIZE'
#define Py_SIZE(ob)             (((PyVarObject*)(ob))->ob_size)
                                 ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:47:
c/vcompiler.c:609:42: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
  ...CompileTime_Get(vindex->source)->value);
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~
c/vcompiler.c:678:42: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
  ...CompileTime_Get(vindex->source)->value,
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:48:
c/psyfunc.c:58:16: warning: implicit conversion loses integer precision:
      'Py_ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
  int ncells = PyTuple_GET_SIZE(co->co_cellvars);
      ~~~~~~   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/tupleobject.h:51:33: note:
      expanded from macro 'PyTuple_GET_SIZE'
#define PyTuple_GET_SIZE(op)    Py_SIZE(op)
                                ^~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/object.h:116:56: note:
      expanded from macro 'Py_SIZE'
#define Py_SIZE(ob)             (((PyVarObject*)(ob))->ob_size)
                                 ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:48:
c/psyfunc.c:59:16: warning: implicit conversion loses integer precision:
      'Py_ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
  int nfrees = PyTuple_GET_SIZE(co->co_freevars);
      ~~~~~~   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/tupleobject.h:51:33: note:
      expanded from macro 'PyTuple_GET_SIZE'
#define PyTuple_GET_SIZE(op)    Py_SIZE(op)
                                ^~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/object.h:116:56: note:
      expanded from macro 'Py_SIZE'
#define Py_SIZE(ob)             (((PyVarObject*)(ob))->ob_size)
                                 ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:48:
c/psyfunc.c:307:55: warning: implicit conversion loses integer precision: 'long'
      to 'int' [-Wshorten-64-to-32]
  po->pr.next_instr = v ? CompileTime_Get(v->source)->value : 0;
                    ~     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~
c/psyfunc.c:322:30: warning: implicit conversion loses integer precision:
      'Py_ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
  int defcount = (defaults ? PyTuple_GET_SIZE(defaults) : 0);
      ~~~~~~~~               ^~~~~~~~~~~~~~~~~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/tupleobject.h:51:33: note:
      expanded from macro 'PyTuple_GET_SIZE'
#define PyTuple_GET_SIZE(op)    Py_SIZE(op)
                                ^~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/object.h:116:56: note:
      expanded from macro 'Py_SIZE'
#define Py_SIZE(ob)             (((PyVarObject*)(ob))->ob_size)
                                 ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:48:
c/psyfunc.c:325:55: warning: implicit conversion loses integer precision:
      'Py_ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
                           &PyTuple_GET_ITEM(arg, 0), PyTuple_GET_SIZE(arg),
                                                      ^~~~~~~~~~~~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/tupleobject.h:51:33: note:
      expanded from macro 'PyTuple_GET_SIZE'
#define PyTuple_GET_SIZE(op)    Py_SIZE(op)
                                ^~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/object.h:116:56: note:
      expanded from macro 'Py_SIZE'
#define Py_SIZE(ob)             (((PyVarObject*)(ob))->ob_size)
                                 ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:48:
c/psyfunc.c:801:27: warning: incompatible pointer types passing 'int *' to
      parameter of type 'Py_ssize_t *' (aka 'long *')
      [-Wincompatible-pointer-types]
                        while (PyDict_Next(kw, &pos, &k[i], &k[i+1]))
                                               ^~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/dictobject.h:115:31: note:
      passing argument to parameter 'pos' here
    PyObject *mp, Py_ssize_t *pos, PyObject **key, PyObject **value);
                              ^
In file included from c/psyco.c:14:
In file included from c/initialize.h:48:
c/psyfunc.c:633:8: warning: implicit conversion loses integer precision:
      'Py_ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
        key = PyTuple_GET_SIZE(arg);
            ~ ^~~~~~~~~~~~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/tupleobject.h:51:33: note:
      expanded from macro 'PyTuple_GET_SIZE'
#define PyTuple_GET_SIZE(op)    Py_SIZE(op)
                                ^~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/object.h:116:56: note:
      expanded from macro 'Py_SIZE'
#define Py_SIZE(ob)             (((PyVarObject*)(ob))->ob_size)
                                 ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:48:
c/psyfunc.c:665:8: warning: implicit conversion loses integer precision:
      'Py_ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
                        i = PyTuple_GET_SIZE(self->psy_defaults);
                          ~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/tupleobject.h:51:33: note:
      expanded from macro 'PyTuple_GET_SIZE'
#define PyTuple_GET_SIZE(op)    Py_SIZE(op)
                                ^~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/object.h:116:56: note:
      expanded from macro 'Py_SIZE'
#define Py_SIZE(ob)             (((PyVarObject*)(ob))->ob_size)
                                 ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:48:
c/psyfunc.c:707:13: warning: implicit conversion loses integer precision: 'long'
      to 'int' [-Wshorten-64-to-32]
                i = key+1 - PyList_GET_SIZE(self->psy_fastcall);
                  ~ ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
c/psyfunc.c:785:9: warning: implicit conversion loses integer precision:
      'Py_ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
                        nd = PyTuple_Size(argdefs);
                           ~ ^~~~~~~~~~~~~~~~~~~~~
c/psyfunc.c:794:9: warning: implicit conversion loses integer precision:
      'Py_ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
                        nk = PyDict_Size(kw);
                           ~ ^~~~~~~~~~~~~~~
c/psyfunc.c:812:31: warning: implicit conversion loses integer precision:
      'Py_ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
                        &PyTuple_GET_ITEM(arg, 0), PyTuple_Size(arg),
                                                   ^~~~~~~~~~~~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:49:
c/stats.c:260:37: warning: incompatible pointer types passing 'int *' to
      parameter of type 'Py_ssize_t *' (aka 'long *')
      [-Wincompatible-pointer-types]
        while (PyDict_Next(codestats_dict, &i, &key, &value)) {
                                           ^~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/dictobject.h:115:31: note:
      passing argument to parameter 'pos' here
    PyObject *mp, Py_ssize_t *pos, PyObject **key, PyObject **value);
                              ^
In file included from c/psyco.c:14:
In file included from c/initialize.h:49:
c/stats.c:298:37: warning: incompatible pointer types passing 'int *' to
      parameter of type 'Py_ssize_t *' (aka 'long *')
      [-Wincompatible-pointer-types]
        while (PyDict_Next(codestats_dict, &i, &key, &value)) {
                                           ^~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/dictobject.h:115:31: note:
      passing argument to parameter 'pos' here
    PyObject *mp, Py_ssize_t *pos, PyObject **key, PyObject **value);
                              ^
In file included from c/psyco.c:14:
In file included from c/initialize.h:49:
c/stats.c:326:37: warning: incompatible pointer types passing 'int *' to
      parameter of type 'Py_ssize_t *' (aka 'long *')
      [-Wincompatible-pointer-types]
        while (PyDict_Next(codestats_dict, &k, &key, &value)) {
                                           ^~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/dictobject.h:115:31: note:
      passing argument to parameter 'pos' here
    PyObject *mp, Py_ssize_t *pos, PyObject **key, PyObject **value);
                              ^
In file included from c/psyco.c:14:
In file included from c/initialize.h:50:
c/profile.c:421:11: warning: implicit conversion loses integer precision: 'long'
      to 'int' [-Wshorten-64-to-32]
                                rec = PyInt_AS_LONG(cs->st_globals);
                                    ~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/intobject.h:52:51: note:
      expanded from macro 'PyInt_AS_LONG'
#define PyInt_AS_LONG(op) (((PyIntObject *)(op))->ob_ival)
                           ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:50:
c/profile.c:483:10: warning: implicit conversion loses integer precision: 'long'
      to 'int' [-Wshorten-64-to-32]
                        rec = PyInt_AS_LONG(cs->st_globals);
                            ~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/intobject.h:52:51: note:
      expanded from macro 'PyInt_AS_LONG'
#define PyInt_AS_LONG(op) (((PyIntObject *)(op))->ob_ival)
                           ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:53:
c/codemanager.c:37:33: warning: implicit conversion loses integer precision:
      'long' to 'int' [-Wshorten-64-to-32]
      num_bigblocks = allocated / BIG_BUFFER_SIZE;
                    ~ ~~~~~~~~~~^~~~~~~~~~~~~~~~~
c/codemanager.c:235:29: warning: format specifies type 'int' but the argument
      has type 'long' [-Wformat]
    fprintf(stderr, "[%d]", codeend - ((code_t*)obj->codestart));
                      ~~    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                      %ld
In file included from c/psyco.c:14:
In file included from c/initialize.h:54:
c/codegen.c:785:38: warning: implicit conversion loses integer precision: 'long'
      to 'int' [-Wshorten-64-to-32]
        return bint_lshift_i(po, v1, counter);
               ~~~~~~~~~~~~~         ^~~~~~~
c/codegen.c:846:38: warning: implicit conversion loses integer precision: 'long'
      to 'int' [-Wshorten-64-to-32]
        return bint_rshift_i(po, v1, counter);
               ~~~~~~~~~~~~~         ^~~~~~~
c/codegen.c:872:39: warning: implicit conversion loses integer precision: 'long'
      to 'int' [-Wshorten-64-to-32]
        return bint_urshift_i(po, v1, counter);
               ~~~~~~~~~~~~~~         ^~~~~~~
In file included from c/psyco.c:14:
In file included from c/initialize.h:55:
c/mergepoints.c:242:3: error: use of undeclared identifier 'JUMP_IF_FALSE'
  F(0x00), F(0x01), F(0x02), F(0x03), F(0x04), F(0x05), F(0x06), F(0x07),
  ^
c/mergepoints.c:230:22: note: expanded from macro 'F'
                    (HAS_JREL_INSTR(op)   ? MP_HAS_JREL       : 0) |    \
                     ^
c/mergepoints.c:50:37: note: expanded from macro 'HAS_JREL_INSTR'
                              op == JUMP_IF_FALSE ||  \
                                    ^
c/mergepoints.c:242:3: error: use of undeclared identifier 'JUMP_IF_TRUE'
c/mergepoints.c:230:22: note: expanded from macro 'F'
                    (HAS_JREL_INSTR(op)   ? MP_HAS_JREL       : 0) |    \
                     ^
c/mergepoints.c:51:37: note: expanded from macro 'HAS_JREL_INSTR'
                              op == JUMP_IF_TRUE ||   \
                                    ^
c/mergepoints.c:242:3: error: use of undeclared identifier 'JUMP_IF_FALSE'
c/mergepoints.c:233:22: note: expanded from macro 'F'
                    (IS_LIGHT_INSTR(op)   ? MP_LIGHT          : 0) |    \
                     ^
c/mergepoints.c:77:30: note: expanded from macro 'IS_LIGHT_INSTR'
                             HAS_JREL_INSTR(op) ||      \
                             ^
c/mergepoints.c:50:37: note: expanded from macro 'HAS_JREL_INSTR'
                              op == JUMP_IF_FALSE ||  \
                                    ^
c/mergepoints.c:242:3: error: use of undeclared identifier 'JUMP_IF_TRUE'
c/mergepoints.c:233:22: note: expanded from macro 'F'
                    (IS_LIGHT_INSTR(op)   ? MP_LIGHT          : 0) |    \
                     ^
c/mergepoints.c:77:30: note: expanded from macro 'IS_LIGHT_INSTR'
                             HAS_JREL_INSTR(op) ||      \
                             ^
c/mergepoints.c:51:37: note: expanded from macro 'HAS_JREL_INSTR'
                              op == JUMP_IF_TRUE ||   \
                                    ^
c/mergepoints.c:242:12: error: use of undeclared identifier 'JUMP_IF_FALSE'
  F(0x00), F(0x01), F(0x02), F(0x03), F(0x04), F(0x05), F(0x06), F(0x07),
           ^
c/mergepoints.c:230:22: note: expanded from macro 'F'
                    (HAS_JREL_INSTR(op)   ? MP_HAS_JREL       : 0) |    \
                     ^
c/mergepoints.c:50:37: note: expanded from macro 'HAS_JREL_INSTR'
                              op == JUMP_IF_FALSE ||  \
                                    ^
c/mergepoints.c:242:12: error: use of undeclared identifier 'JUMP_IF_TRUE'
c/mergepoints.c:230:22: note: expanded from macro 'F'
                    (HAS_JREL_INSTR(op)   ? MP_HAS_JREL       : 0) |    \
                     ^
c/mergepoints.c:51:37: note: expanded from macro 'HAS_JREL_INSTR'
                              op == JUMP_IF_TRUE ||   \
                                    ^
c/mergepoints.c:242:12: error: use of undeclared identifier 'JUMP_IF_FALSE'
c/mergepoints.c:233:22: note: expanded from macro 'F'
                    (IS_LIGHT_INSTR(op)   ? MP_LIGHT          : 0) |    \
                     ^
c/mergepoints.c:77:30: note: expanded from macro 'IS_LIGHT_INSTR'
                             HAS_JREL_INSTR(op) ||      \
                             ^
c/mergepoints.c:50:37: note: expanded from macro 'HAS_JREL_INSTR'
                              op == JUMP_IF_FALSE ||  \
                                    ^
c/mergepoints.c:242:12: error: use of undeclared identifier 'JUMP_IF_TRUE'
c/mergepoints.c:233:22: note: expanded from macro 'F'
                    (IS_LIGHT_INSTR(op)   ? MP_LIGHT          : 0) |    \
                     ^
c/mergepoints.c:77:30: note: expanded from macro 'IS_LIGHT_INSTR'
                             HAS_JREL_INSTR(op) ||      \
                             ^
c/mergepoints.c:51:37: note: expanded from macro 'HAS_JREL_INSTR'
                              op == JUMP_IF_TRUE ||   \
                                    ^
c/mergepoints.c:242:21: error: use of undeclared identifier 'JUMP_IF_FALSE'
  F(0x00), F(0x01), F(0x02), F(0x03), F(0x04), F(0x05), F(0x06), F(0x07),
                    ^
c/mergepoints.c:230:22: note: expanded from macro 'F'
                    (HAS_JREL_INSTR(op)   ? MP_HAS_JREL       : 0) |    \
                     ^
c/mergepoints.c:50:37: note: expanded from macro 'HAS_JREL_INSTR'
                              op == JUMP_IF_FALSE ||  \
                                    ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
40 warnings and 20 errors generated.
error: command 'cc' failed with exit status 1
Bobs-iMac:psyco-1.6 19.48.55 boblishman$


I cannot get Max3ds 7 to install (via Wineskin) so my only option is to use Blender 2.49b and Pyprp.
Blender 2.49b runs (just about, horrible but just about useable) and I have managed to install everything else needed (Crypto, PIL and YAML).

Any help would be gratefully received.

[Christian Walther]

Unfortunately I can’t find a complete solution for you as I only have Mavericks in a virtual machine with no OpenGL, but here are a few bits and pieces:

• At the time PyPRP 1.6.0 was developed, it worked for me on Mac OS X, although that was probably on 10.4 or 10.5. I don’t think I’ve tried it on later versions.
• Psyco is not required to run PyPRP.
• I wonder if the SystemError is a variant of this Google result.

Is the age you’re trying to export one that has exported successfully in the past on other computers, or is it a completely new one? With PyPRP’s inexistent error handling, you can never be sure whether such an exception indicates a problem with your input or a problem with PyPRP…

[Sirius]

I actually believe the error is very simple and unrelated to Mac, as you said you're using Blender and Python in 64 bits, while Psyco is 32 bits only.

Have a look at the error message:

Sorry, non-32-bit platforms are not supported at all. You may try with a Python compiled in 32-bit compatibility mode. Note that Psyco will probably never support non-32-bit platforms, as it is no longer actively developed. Instead, the PyPy group plans to replace it with a more flexible and easily retargettable Psyco-for-PyPy during the year 2006. See http://codespeak.net/pypy/

I'd suggest reinstalling a 32 bit version of Blender, Python and the two required libraries (it will work the same even on a 64 bit computer). I'm quite sure this will solve the problem.

[Christian Walther]

as you said you're using Blender and Python in 64 bits

He didn’t say that, and he isn’t (unless he’s using something different than the official binary release). The official “blender-2.49b-OSX-10.5-py2.5-intel” release that he appears to be using was 32-bit only, as far as I can see, and so must be the Python 2.5 installation used with it. Only the Python 2.7 that he’s trying to install Psyco into is 64-bit. It’s the wrong installation of Python but that doesn’t matter as Psyco isn’t required.

[boblishman]

Christian, I've tried both. An "old" Age I made for the RAD contest plus a simple new one (a single textured cube, a sun, and a link in point. Both fail to export when it tries to compress the textures.

There is only ONE version of BLENDER 2.49b available to download for MacOSX Intel and I've managed to install the YAML and PIL by installing them and then copying the folders from Python 2.7 to 2.5. At the begining it complained about not having "imaging" and YAML. That doesn't happen now. During the export it runs fine until it reaches the part where the textures are compressed. As you can see,it does 512 and then 256 and then gets itself all screwed up.

I am no coder ... so the Google result may as well be in Chinese as I have no idea what it means. Looking again though, the Blender console does clearly say the the error is happening in PIL.

(If psychos isn't needed, why does the console window say "psyco not availble to pyprp" ?)

[Deledrius]

(If psychos isn't needed, why does the console window say "psyco not availble to pyprp" ?)

Because it's not available, and it's making note of that. It's not an error, just information. Psyco helps speed the process up but is not required.

[Christian Walther]

Christian, I've tried both. An "old" Age I made for the RAD contest plus a simple new one (a single textured cube, a sun, and a link in point. Both fail to export when it tries to compress the textures.

Good, so we can rule out a problem with the age.

I've managed to install the YAML and PIL by installing them and then copying the folders from Python 2.7 to 2.5.

Eek, that sounds suspicious. It may or may not be the cause of your problem, but you should try installing them into the proper Python installation to begin with. I don’t expect binary modules built for one version of Python to work for another. Instead of using the python command to install them (which is Python 2.7), you need to use the one of Python 2.5. I don’t know for sure where that is, but I can make some guesses and you can check if any of them is correct. Can you post the output of running the following commands in a terminal?

Code: Select all

which python2.5
python2.5 -c "import sys; print sys.path"
/System/Library/Frameworks/Python.framework/Versions/2.5/bin/python -c "import sys; print sys.path"
/Library/Frameworks/Python.framework/Versions/2.5/bin/python -c "import sys; print sys.path"

I am no coder ... so the Google result may as well be in Chinese as I have no idea what it means.

Yeah, that wasn’t specifically aimed at you, more thinking aloud aimed at other coders.

[Sirius]

Alright, I thought this was the error because Boblishman said it "won't install on 64 bits". Nevermind me, then.

[boblishman]

Can you post the output of running the following commands in a terminal?

Code: Select all

which python2.5
python2.5 -c "import sys; print sys.path"
/System/Library/Frameworks/Python.framework/Versions/2.5/bin/python -c "import sys; print sys.path"
/Library/Frameworks/Python.framework/Versions/2.5/bin/python -c "import sys; print sys.path"

Here's what it says ... and, although I'm no coder, I have a feeling we may be getting nearer the problem ...

Code: Select all

Last login: Sat Jun 28 13:37:29 on ttys002
Bobs-iMac:~ boblishman$ which python2.5
/usr/bin/python2.5
Bobs-iMac:~ boblishman$
Bobs-iMac:~ boblishman$

Bobs-iMac:~ boblishman$ python2.5 -c "import sys; print sys.path"
['', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python25.zip', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/plat-darwin', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/plat-mac', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/plat-mac/lib-scriptpackages', '/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/lib-tk', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/lib-dynload', '/Library/Python/2.5/site-packages', '/Library/Python/2.5/site-packages/PIL', '/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/PyObjC']
Bobs-iMac:~ boblishman$

 
Bobs-iMac:~ boblishman$
Bobs-iMac:~ boblishman$ /System/Library/Frameworks/Python.framework/Versions/2.5/bin/python -c "import sys; print sys.path"
['', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python25.zip', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/plat-darwin', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/plat-mac', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/plat-mac/lib-scriptpackages', '/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/lib-tk', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/lib-dynload', '/Library/Python/2.5/site-packages', '/Library/Python/2.5/site-packages/PIL', '/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/PyObjC']
Bobs-iMac:~ boblishman$
Bobs-iMac:~ boblishman$
Bobs-iMac:~ boblishman$ /Library/Frameworks/Python.framework/Versions/2.5/bin/python -c "import sys; print sys.path"
-bash: /Library/Frameworks/Python.framework/Versions/2.5/bin/python: No such file or directory
Bobs-iMac:~ boblishman$



Christian, I am very, very grateful for your help on this. Let me explain a few things. I now share this Mac with my other half and we have separate user accounts (because we both have different mother tongues : English/Spanish) and I have never used Terminal before and, in truth, know almost nothing about how it works other than using the "sudo" command is dangerous if you don't know what you're doing (which I don't !).
This Mac is the ONLY computer we have at home. It's taken me six months to get both our accounts set up and working EXACTLY how we want them to be and I'm TERRIFIED of doing anything that may screw up this machines system and create a need for a re-install. My life would (seriously!) not be worth living if I screwed up the machine and lost my other half's data, settings and software. Yes, I know we need en external hard drive to back everything up regularly but I have yet to buy one (though I certainly will in the coming months) so maybe you can see my trepidation in using Terminal. Having said that, I trust YOU implicitly and any instructions you may have for me.

Installing YAML and PIL: It would not let me install without using the "sudo" command before "python setup.py install" as it wouldn't create the directory. (I had read about using sudo somewhere)
So I "bit the bullet" and used "sudo python setup.py install" and then it DID put them into ... Python 2.7.

I had (and still haven't) no idea how to install them directly into Python 2.5, so I tried copying and pasting them into 2.5's directory (site packages) and then did an export ... and the console stopped complaining about YAML. I exported my new, untextured Age (cube, spawn point, sun) which completed successfully, and copied the files into my dat folder in my offline CC and visited it with the offline KI ... and it worked perfectly. I then textured the cube ... and that's when this exporting error started. I tested my old RAD age (which I know exported perfectly on Windows) and got the exact same error.

So, in short, I probably haven't installed PIL or YAML properly, and that's easy to "undo" because I can just put those directories in the trash and start again. If you can tell me exactly how to install them directly into the Python 2.5 directory, I will follow your instructions to the letter and report back what happens.

Here is a screenshot to prove the Python 2.5 directory DOES exist ... (though, it may be a different one to the one you want so I've included the "get info" for you ???)

Show Spoiler

Finally, I have read somewhere (just before my head exploded) about a way to run Blender in a "32bit environment" using a Terminal command ... but, as I said, that's when my head exploded as I have no desire to screw up OUR machine and have my "crown jewels" forcibly removed by my other half, which is undoubtedly what would happen, however, I am wondering if this would stop the incessant screen flicker in Blender ?

Again, many, many thanks for your time, and I look forward to your response.

[Christian Walther]

Thanks Bob, that information helps. The terminal output confirms that what you reach under “python2.5” is the one we want (it looks into the same /Library/Python/2.5/site-packages folder as mentioned in your Blender output).

You are right that sudo should be used as little as possible because it lets you do dangerous things. In this case, the things we do are unlikely to screw up anything big time, as we are dealing with known and trusted software and nothing else than your Python 2.5 installation, which probably isn’t used by anything other than Blender, should be affected. (But do get that backup harddrive anyway, backing up with Time Machine is really painless and saves you tons of trouble also in other cases!)

The reason why it worked halfways and the untextured export succeeded, if my suspicions are correct, is that in that case only parts of PyYAML and possibly PIL were used that are written in Python and work unmodified on both versions 2.5 and 2.7, while to export textures it was trying to use parts of PIL that are written in C and were specifically built for Python 2.7.

So, what you should do now is:

1. Remove all the files and folders you manually moved into the /Library/Python/2.5/site-packages folder (you can put them back into 2.7 if you think you’ll ever have a use for them there, or just trash them).
2. Install these things again, instead of sudo python setup.py install using sudo python2.5 setup.py install

Keep the terminal output of that around for reference in case anything goes wrong, and try your age export again.

Finally, I have read somewhere (just before my head exploded) about a way to run Blender in a "32bit environment" using a Terminal command ... but, as I said, that's when my head exploded as I have no desire to screw up OUR machine and have my "crown jewels" forcibly removed by my other half, which is undoubtedly what would happen, however, I am wondering if this would stop the incessant screen flicker in Blender ?

I am unsure what could be meant by that, but I doubt it applies to your version of Blender, which is 32-bit-only anyway. I don’t know what causes any “screen flicker”, but it is probably unrelated. Have you tried googling for it to see if anyone else is having the same problem?