By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,799 Members | 1,362 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,799 IT Pros & Developers. It's quick & easy.

Psyco & Linux

P: n/a

Hi All;

I have Psyco (on Windows XP) and now I want to install it on Linux, too.
I FTP'd the tarball (tar.gz) from Psyco's site but can't get it compiled.
First, I tried the usual "python setup.py install" but that did not work.
I later found a RPM for Psyco but it wasn't suitable to the Linux version
I'm currently using.

Has any of you had a similar experience? If so, how did you manage
to solve the problem (in the case that you did)? Before one asks, I
must say that I'm trying to build the package as the super user (root).
:-)

The specifics of my system are:

Athlon AMD-64 3300+
SuSE 9.3 Professional (64-bit)
Python 2.4
gcc/g++ 3.3.5

Thanks in advance for any help.

---Fausto
Aug 12 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a

First, I tried the usual "python setup.py install" but that did not work.


How exactly did it fail? Perhaps you can paste the error output from
this command.

Aug 12 '05 #2

P: n/a

Hi Steve;

Steve M wrote:
First, I tried the usual "python setup.py install" but that did not work.
How exactly did it fail? Perhaps you can paste the error output from
this command.


Sure, he is the output:

linux:/home/fausto/Documents/psyco-1.4 # python setup.py install
PROCESSOR = 'ivm'
Copying c/ivm/prolog/insns-igen-h.i.default -> c/ivm/prolog/insns-igen-h.i
Copying c/ivm/prolog/insns-threaded.i.default -> c/ivm/prolog/insns-threaded.i
Copying c/ivm/prolog/insns-switch.i.default -> c/ivm/prolog/insns-switch.i
Copying c/ivm/prolog/insns-igen.i.default -> c/ivm/prolog/insns-igen.i
Copying c/ivm/prolog/mode_combine.pl.default -> c/ivm/prolog/mode_combine.pl
Copying c/ivm/prolog/insns-table.py.default -> c/ivm/prolog/insns-table.py
running install
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.4
creating build/lib.linux-x86_64-2.4/psyco
copying psyco/core.py -> build/lib.linux-x86_64-2.4/psyco
copying psyco/kdictproxy.py -> build/lib.linux-x86_64-2.4/psyco
copying psyco/logger.py -> build/lib.linux-x86_64-2.4/psyco
copying psyco/profiler.py -> build/lib.linux-x86_64-2.4/psyco
copying psyco/support.py -> build/lib.linux-x86_64-2.4/psyco
copying psyco/__init__.py -> build/lib.linux-x86_64-2.4/psyco
copying psyco/classes.py -> build/lib.linux-x86_64-2.4/psyco
running build_ext
building 'psyco._psyco' extension
creating build/temp.linux-x86_64-2.4
creating build/temp.linux-x86_64-2.4/c
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -fmessage-length=0 -Wall -g -fPIC -DALL_STATIC=1
-Ic/ivm -I/usr/include/python2.4 -c c/psyco.c -o build/temp.linux-x86_64-2.4/c/psyco.o
In file included from c/dispatcher.h:12,
from c/codemanager.h:10,
from c/psyco.c:3:
c/codegen.h:19:3: #error "sorry -- I guess it won't work like that on 64-bits machines"
In file included from c/initialize.h:46,
from c/psyco.c:13:
c/dispatcher.c: In function `fz_compress':
c/dispatcher.c:232: warning: cast from pointer to integer of different size
c/dispatcher.c:238: warning: cast to pointer from integer of different size
In file included from c/initialize.h:53,
from c/psyco.c:13:
c/codemanager.c: In function `psyco_shrink_code_buffer':
c/codemanager.c:252: warning: int format, different type arg (arg 3)
In file included from c/initialize.h:61,
from c/psyco.c:13:
c/Objects/pabstract.c:716:3: #error "omitted code from Python 2.3 here"
In file included from c/initialize.h:75,
from c/psyco.c:13:
c/Objects/pstructmember.c: In function `PsycoMember_GetOne':
c/Objects/pstructmember.c:16: warning: unused variable `w2'
c/Objects/compactobject.c: At top level:
c/codegen.c:711: warning: `integer_lshift' defined but not used
c/ivm/prolog/insns-igen.i:175: warning: `psyco_insn_assertdepth' defined but not used
c/ivm/prolog/insns-igen.i:197: warning: `psyco_insn_dynamicfreq' defined but not used
c/Objects/plongobject.c:21: warning: `PsycoLong_AsDouble' defined but not used
c/Objects/plistobject.c:116: warning: `PsycoList_SingletonNew' defined but not used
error: command 'gcc' failed with exit status 1

Any ideas? ;-) Clueless in Edmonton...

---Fausto

Aug 12 '05 #3

P: n/a
Fausto Arinos Barbuto wrote:
The specifics of my system are:

Athlon AMD-64 3300+
SuSE 9.3 Professional (64-bit)
Python 2.4
gcc/g++ 3.3.5


Ummm... I thought psyco only supported 32 bit systems. I haven't seen
anything else to suggest otherwise. See

http://psyco.sourceforge.net/psycoguide/req.html

Maybe you could recompile your python in 32 bit mode. You may find that
native 64 bit python is faster than 32 bit psyco however!

--
Jeremy Sanders
http://www.jeremysanders.net/
Aug 12 '05 #4

P: n/a
"Jeremy Sanders" <je*******************@jeremysanders.net> wrote in
message
Fausto Arinos Barbuto wrote:
The specifics of my system are:

Athlon AMD-64 3300+
SuSE 9.3 Professional (64-bit)
Python 2.4
gcc/g++ 3.3.5

Ummm... I thought psyco only supported 32 bit systems. I haven't seen
anything else to suggest otherwise. See
You're probably right. I will try to compile psyco on another
32-bit Linux box I have.
Maybe you could recompile your python in 32 bit mode. You may find that
native 64 bit python is faster than 32 bit psyco however!


When properly designed, scripts using Psyco are so much faster
than the original code that I doubt native 64-bit Python can
defeat it in terms of speed. A fair benchmark though could
only be carried out if I had a 64-bit version of Psyco. I
guess I 'll have to wait for one.

Thanks for your reply.

---Fausto

Aug 12 '05 #5

P: n/a
> c/codegen.h:19:3: #error "sorry -- I guess it won't work like that on 64-bits machines"

The first error output by gcc suggests the 64-bit OS might be the
problem. But I don't actually know what that error means.

Aug 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.