Source: rhash Version: 1.2.9-5 Severity: serious Tags: wheezy sid User: [email protected] Usertags: qa-ftbfs-20120604 qa-ftbfs User: [email protected] Usertags: default19 Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory `/«PKGBUILDDIR»/bindings/perl' > cp Rhash.pm blib/lib/Rhash.pm > /usr/bin/perl /usr/share/perl/5.14/ExtUtils/xsubpp -typemap > /usr/share/perl/5.14/ExtUtils/typemap -typemap typemap Rhash.xs > Rhash.xsc > && mv Rhash.xsc Rhash.c > cc -c -I/«PKGBUILDDIR»/debian/tmp -D_REENTRANT -D_GNU_SOURCE -DDEBIAN > -fstack-protector -fno-strict-aliasing -pipe -I/usr/local/include > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -Wall -DVERSION=\"0.01\" > -DXS_VERSION=\"0.01\" -fPIC "-I/usr/lib/perl/5.14/CORE" Rhash.c > Running Mkbootstrap for Rhash () > chmod 644 Rhash.bs > rm -f blib/arch/auto/Rhash/Rhash.so > LD_RUN_PATH="/«PKGBUILDDIR»/debian/tmp" cc -shared -L/usr/local/lib > -fstack-protector Rhash.o -o blib/arch/auto/Rhash/Rhash.so \ > -L/«PKGBUILDDIR»/debian/tmp -lrhash \ > > chmod 755 blib/arch/auto/Rhash/Rhash.so > cp Rhash.bs blib/arch/auto/Rhash/Rhash.bs > chmod 644 blib/arch/auto/Rhash/Rhash.bs > Manifying blib/man3/Rhash.3pm > make[2]: Leaving directory `/«PKGBUILDDIR»/bindings/perl' > ruby -C ruby extconf.rb > /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load > such file -- mkmf (LoadError) > from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' > from extconf.rb:1:in `<main>' > make[1]: *** [ruby/Makefile] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/04/rhash_1.2.9-5_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]
