Source: binutils-avr
Version: 2.26.20160125+Atmel3.6.2-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<<PKGBUILDDIR>>/binutils/libiberty/testsuite'
> make[4]: Nothing to be done for 'install'.
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/binutils/libiberty/testsuite'
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/binutils/libiberty'
> make[2]: Nothing to be done for 'install-target'.
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/binutils'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>/binutils'
> #cp debian/gasp.1 debian/binutils-avr/usr/share/man/man1/avr-gasp.1
> # Non standard avr dir to keep FHS happy
> mv debian/binutils-avr/usr/avr debian/binutils-avr/usr/lib/
> # Convert hardlinks to softlinks
> cd debian/binutils-avr/usr/lib/avr/bin && for f in *; do \
>     rm ../../../bin/avr-$f; \
>     ln -s ../lib/avr/bin/$f ../../../bin/avr-$f; \
> done
> /bin/sh: 1: cd: can't cd to debian/binutils-avr/usr/lib/avr/bin
> make: *** [debian/rules:88: install] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/binutils-avr_2.26.20160125+Atmel3.6.2-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230726&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Reply via email to