Package: geda-xgsch2pcb
version: 0.1.2-1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080205 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
Relevant part:
> checking for python... /usr/bin/python
> checking for python version... 2.4
> checking for python platform... linux2
> checking for python script directory... ${prefix}/lib/python2.4/site-packages
> checking for python extension module directory...
> ${exec_prefix}/lib/python2.4/site-packages
> checking for style of include used by make... GNU
> checking for i486-linux-gnu-gcc... i486-linux-gnu-gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether i486-linux-gnu-gcc accepts -g... yes
> checking for i486-linux-gnu-gcc option to accept ISO C89... none needed
> checking dependency style of i486-linux-gnu-gcc... none
> checking for intltool >= 0.35.0... 0.36.2 found
> checking for perl... /usr/bin/perl
> checking for XML::Parser... configure: error: XML::Parser perl module is
> required for intltool
> make: *** [config.status] Error 1
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
The full build log is available from:
http://people.debian.org/~lucas/logs/2008/02/05
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
