Source: farpd
Version: 0.2-10
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
>  debian/rules build
> dh_testdir
> # Add here commands to configure the package.
> ./configure --host=x86_64-linux-gnu --build=x86_64-linux-gnu --prefix=/usr 
> --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
> creating cache ./config.cache
> checking for a BSD compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... yes
> checking for working aclocal... missing
> checking for working autoconf... missing
> checking for working automake... missing
> checking for working autoheader... missing
> checking for working makeinfo... missing
> checking for mawk... mawk
> checking for gcc... gcc
> checking whether the C compiler (gcc  ) works... yes
> checking whether the C compiler (gcc  ) is a cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> checking for a BSD compatible install... /usr/bin/install -c
> checking whether ln -s works... yes
> checking for socket in -lsocket... no
> checking for gethostbyname in -lnsl... yes
> configure: error: libevent not found
> checking for libdumbnet... yes
> checking for libevent... no
> make: *** [config.status] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/farpd_0.2-10_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to