Source: seabios
Version: 1.8.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> Build Kconfig config file
> Compile checking build/bios/src/misc.o
> In file included from src/misc.c:13:0:
> src/string.h:18:13: warning: inline function 'memcpy_far' declared but never
> defined
> inline void memcpy_far(u16 d_seg, void *d_far
> ^~~~~~~~~~
> src/string.h:15:13: warning: inline function 'memset16_far' declared but
> never defined
> inline void memset16_far(u16 d_seg, void *d_far, u16 c, size_t len);
> ^~~~~~~~~~~~
> src/string.h:14:13: warning: inline function 'memset_far' declared but never
> defined
> inline void memset_far(u16 d_seg, void *d_far, u8 c, size_t len);
> ^~~~~~~~~~
> Compile checking build/bios/src/stacks.o
> src/stacks.c: Assembler messages:
> src/stacks.c:635: Error: found '(', expected: ')'
> src/stacks.c:635: Error: junk `(%ebp))' after expression
> src/stacks.c:636: Warning: indirect call without `*'
> Makefile:129: recipe for target 'build/bios/src/stacks.o' failed
> make[1]: *** [build/bios/src/stacks.o] Error 1
If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185
If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.
The full build log is available from:
http://aws-logs.debian.net/2016/10/21/seabios_1.8.2-1_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.
