python-gnome na builderze i586

[Grzegorz Goławski]

Na builderze i586 nie zbudował się python-gnome. Na pozostałych
przeszedł bez problemów. Oto log:

[...]
i586-pld-linux-gcc -shared  .libs/canvas_la-canvasmodule.o .libs/canvas_la-canvas.o  -Wl,--rpath -Wl,/usr/X11R6/lib -Wl,--rpath -Wl,/usr/X11R6/lib -L/usr/lib -L/usr/X11R6/lib /usr/lib/libgnomecanvas-2.so /usr/lib/libart_lgpl_2.so /usr/lib/libpangoft2-1.0.so /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so -lXi -lXinerama -lXext /usr/X11R6/lib/libXcursor.so /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so -lm /usr/lib/libpangoxft-1.0.so /usr/X11R6/lib/libXft.so /usr/lib/libfreetype.so -lz /usr/X11R6/lib/libXrender.so /usr/lib/libfontconfig.so /usr/lib/libpangox-1.0.so -lX11 /usr/lib/libpango-1.0.so /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libglib-2.0.so  -march=i586 -Wl,-soname -Wl,canvas.so -Wl,-version-script -Wl,.libs/canvas.ver -o .libs/canvas.so
creating canvas.la
(cd .libs && rm -f canvas.la && ln -s ../canvas.la canvas.la)
if /bin/sh ../libtool --mode=compile i586-pld-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/python2.3 -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include     -pthread -DORBIT2=1 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/bonobo-activation-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/pyorbit-2   -O2 -march=i586 -Wall -std=c9x -fno-strict-aliasing -MT vfs_la-vfsmodule.lo -MD -MP -MF ".deps/vfs_la-vfsmodule.Tpo" \
  -c -o vfs_la-vfsmodule.lo `test -f 'vfsmodule.c' || echo './'`vfsmodule.c; \
then mv -f ".deps/vfs_la-vfsmodule.Tpo" ".deps/vfs_la-vfsmodule.Plo"; \
else rm -f ".deps/vfs_la-vfsmodule.Tpo"; exit 1; \
fi
 i586-pld-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/python2.3 -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -DORBIT2=1 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/bonobo-activation-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/pyorbit-2 -O2 -march=i586 -Wall -std=c9x -fno-strict-aliasing -MT vfs_la-vfsmodule.lo -MD -MP -MF .deps/vfs_la-vfsmodule.Tpo -c vfsmodule.c  -fPIC -DPIC -o .libs/vfs_la-vfsmodule.o
In file included from vfsmodule.c:5:
/usr/include/pyorbit-2/pyorbit.h:1: error: stray '\1' in program
In file included from vfsmodule.c:5:
/usr/include/pyorbit-2/pyorbit.h:1:2: warning: null character(s) ignored
/usr/include/pyorbit-2/pyorbit.h:1: error: stray '\3' in program
/usr/include/pyorbit-2/pyorbit.h:1:4: warning: null character(s) ignored
/usr/include/pyorbit-2/pyorbit.h:1: error: stray '\4' in program
/usr/include/pyorbit-2/pyorbit.h:1:6: warning: null character(s) ignored
/usr/include/pyorbit-2/pyorbit.h:1: warning: type defaults to `int' in declaration of `le'
/usr/include/pyorbit-2/pyorbit.h:1: error: `string' undeclared here (not in a function)
[...]

Troche dziwne to jest. Może plik /usr/include/pyorbit-2/pyorbit.h jest uszkodzony?

-- 
Grzegorz Goławski <grzegol w pld-linux.org>