[tahoe-dev] Installation issue

[zooko]

On Nov 13, 2007, at 1:44 PM, Francesco Albanese wrote:

> Hi,
> I'm trying to install allmydata on a small network to make an
> evaluation about the installation feasibility in my university.

Hello Francesco Albanese, thank you for writing.

> Unluckily I'm not able to complete the installation due to compilation
> problems, because gcc can't look up "Python.h" while building pycrypt
> libraries. I know that the above file belongs to Python source code,
> so this should be installed: I wonder if someone could suggest a way
> to resolve the linking on a machine where I have not root privilege.

Okay there are two steps that you need to take.

The first is to get the Python.h onto your filesystem, and make sure  
that it is the version of Python.h that matches the version of python  
that you will use.  You might find that file already installed  
somewhere on your system, and if not then you can start at http:// 
python.org to download python (it comes with the Python.h file).

The second is to inform the build scripts where to find Python.h.   
You can put this in a distutils config file [1], such a by creating a  
file named "setup.cfg" in the top-level directory of the tahoe source  
and putting the following lines into it:

------- begin included setup.cfg file
[build_ext]
include_dirs=$PATH_TO_DIRECTORY_THAT_CONTAINS_PYTHON_HEADER_FILE
------- end included setup.cfg file

Please let us know how it goes!

Regards,

Zooko

[1] http://www.python.org/doc/inst/config-syntax.html