Re: [Pyallegro] Compliation issue. Help?

[Grzegorz A. H. <gr...@ti...>]

On 2007-07-29, Tristan Ankerstar <tr...@an...> wrote:
> ...here's the actual attachment. Whoops.
>
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include -I/usr/include/python2.5 -c _alpymodule.c -o build/temp.linux-i686-2.5/_alpymodule.o -Wno-deprecated-declarations -Werror
> src/_alpymodule.c.in:28:20: error: Python.h: No such file or directory
> src/_alpymodule.c.in:37: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
> src/_alpymodule.c.in:74: error: expected specifier-qualifier-list before ‘PyObject_HEAD’

The first error line tells that Python.h is not found, and therefore all
python related tokens like structures will make the compilation fail.
You will need to get the python-dev package which includes Python's
development headers required to compile native extension modules.

If you already have the package you would have to find out why it is not
being included. By default you can see in the gcc commandline that
distutils is forcing an include of the path /usr/include/python2.5. If
the headers are somewhere else, I think you could create a symbolic link
to them using that path.

Probably easier than modifying distutils, though you should report a
bug to your distro about this.

Talking about packages, you will also need Allegro's development one.