/data/home/nwagner/local/lib/python2.5/pyport.h:734:2: #error
LONG_BIT definition appears wrong for platform (bad gcc/glibc
config?).
Can anyone offer any advice as to what I might be missing or
misunderstanding?
You need to understand where the error comes from:
1. what is the *actual*
Thanks for replying, Martin.
I got my colleague (Nils) to run exactly the gcc call you described in
your post (see below for what he ran) but it only returns the
following:
/home/nwagner/svn/PyDSTool/PyDSTool/tests/dopri853_temp/dop853_HHnet_vf_wrap.c:124:20:
error: Python.h: Datei oder
Rob Clewley wrote:
I got my colleague (Nils) to run exactly the gcc call you described in
your post (see below for what he ran) but it only returns the
following:
Sehr seltsam. Welche gcc-Version ist das denn? (gcc -v)
Hi,
I have a problem compiling legacy C code using distutils on a
colleague's 64 bit intel machine running linux. The legacy code is
linked to user-generated code from python and distutils is a
convenient platform independent way to call whatever compiler is
available to create a DLL as a python
