Re: [rdiff-backup-users] Problem when compiling - can't find Python.h

[Andreas Olsson]

mån 2010-11-22 klockan 14:05 +0000 skrev Chris G:
> I use rdiff-backup to do backups to two external systems where I have
> shell login accounts. Trying to compile version 1.3.3 on *both* of
> these
> systems fails because Python.h is missing:-
> 
>     ...
>     ...
>     ...
>     copying rdiff_backup/user_group.py ->
> build/lib.linux-i686-2.5/rdiff_backup
>     copying rdiff_backup/win_acls.py ->
> build/lib.linux-i686-2.5/rdiff_backup
>     running build_ext
>     building 'rdiff_backup.C' extension
>     creating build/temp.linux-i686-2.5
>     gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -I/usr/include/python2.5 -c cmodule.c -o
> build/temp.linux-i686-2.5/cmodule.o
>     cmodule.c:24:20: error: Python.h: No such file or directory
>     cmodule.c:76: error: expected '=', ',', ';', 'asm' or
> '__attribute__' before '*' token
>     ...
>     ...
>     ...
> 
> So, is this simply because the remote systems don't have some Python
> development headers installed or is there some more subtle problem? 

Yes, this is the exact error you get from missing python dev headers.

(You will also need librsync and its development headers.)

// Andreas

signature.asc
Description: Detta är en digitalt signerad meddelandedel