Package: esperanza
Version: 0.4.0-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080419 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on i386.

This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now
the default on most architectures (even if it's not the case on i386 yet).
Feel free to downgrade this bug to 'important' if your package is only built
on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine with
gcc 4.2).

Relevant part:
>  /usr/bin/fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp configure-stamp
> if test -f Makefile; then \
>               /usr/bin/make distclean; \
>       fi
> rm -f esperanza conf.log conf.pri
> dh_clean
>  dpkg-source -b esperanza-0.4.0
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building esperanza using existing 
> esperanza_0.4.0.orig.tar.gz
> dpkg-source: info: building esperanza in esperanza_0.4.0-2.diff.gz
> dpkg-source: info: building esperanza in esperanza_0.4.0-2.dsc
>  debian/rules build
> dh_testdir
> ./configure --prefix=/usr
> Configuring Esperanza ...
> Verifying Qt 4 build environment ... ok
> Checking for Qt >= 4.2.3 ... yes
> Checking for Xmms2 Client C++ Bindings ... no
> 
> Error: need Xmms2 Client C++ Bindings!
> 
> make: *** [configure-stamp] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/04/19

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]

Reply via email to