Source: binutils-mingw-w64
Version: 2
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[5]: Entering directory `/«PKGBUILDDIR»/build/i686-w64-mingw32/bfd/doc'
> make[5]: `chew' is up to date.
> make[5]: Leaving directory `/«PKGBUILDDIR»/build/i686-w64-mingw32/bfd/doc'
> ./chew -f ../../../../upstream/bfd/doc/doc.str 
> <../../../../upstream/bfd/doc/../linker.c >linker.tmp
> /bin/bash ../../../../upstream/bfd/doc/../../move-if-change linker.tmp 
> linker.texi
> restore=: && backupdir=".am$$" && \
>       rm -rf $backupdir && mkdir $backupdir && \
>       if (makeinfo --split-size=5000000 --split-size=5000000 --version) 
> >/dev/null 2>&1; then \
>         for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] bfd.i[0-9] 
> bfd.i[0-9][0-9]; do \
>           if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
>         done; \
>       else :; fi && \
>       if makeinfo --split-size=5000000 --split-size=5000000   -I 
> ../../../../upstream/bfd/doc \
>        -o bfd.info `test -f 'bfd.texinfo' || echo 
> '../../../../upstream/bfd/doc/'`bfd.texinfo; \
>       then \
>         rc=0; \
>       else \
>         rc=$?; \
>         $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \
>       fi; \
>       rm -rf $backupdir; exit $rc
> ../../../../upstream/bfd/doc/bfd.texinfo:325: unknown command `colophon'
> ../../../../upstream/bfd/doc/bfd.texinfo:336: unknown command `cygnus'
> make[4]: *** [bfd.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/binutils-mingw-w64_2_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