Perforce on PowerPC and Intel
I’ve recently had an interest in reviving my Perforce depot and grabbing some code out of it — unfortunately the depot database I have with me here on my laptop was created on a PowerPC Mac, whereas this is a Core Duo.
I would like to mention to the world that while p4d is pretty endian neutral the database is not. You need to checkpoint your db from the original server (or perhaps a server running the same architecture would be fine) and then import it into the new, little-endian db.
More details at a copy of the Perforce admin manual.
[NOTE: Look at this crap.
src/perforce/api.cpp:3200: error: invalid conversion from ‘int (*)(PyObject*)’ to ‘Py_ssize_t (*)(PyObject*)’
src/perforce/api.cpp: In function ‘PyObject* p4api_FileSys_path(p4api_FileSys*)’:
src/perforce/api.cpp:3896: error: request for member ‘Text’ in ‘#’obj_type_ref’ not supported by dump_expr#(self->p4api_FileSys::myFileSys)’, which is of non-class type ‘StrPtr*’
src/perforce/api.cpp:3897: error: request for member ‘Length’ in ‘#’obj_type_ref’ not supported by dump_expr#(self->p4api_FileSys::myFileSys)’, which is of non-class type ‘StrPtr*’
src/perforce/api.cpp:3200: error: invalid conversion from ‘int (*)(PyObject*)’ to ‘Py_ssize_t (*)(PyObject*)’
… I so don’t miss working in C-based languages.]
About this entry
You’re currently reading “ Perforce on PowerPC and Intel ,” an entry on stuffonfire.com
- Published:
- 6.16.07 / 6am
- Category:
- Programming
No comments
Jump to comment form | comments rss [?] | trackback uri [?]