[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#725575: kfreebsd-8: FTBFS: ctfconvert: No such file or directory



Source: kfreebsd-8
Version: 8.3-6
Severity: serious
Tags: jessie sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20131006 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):
> ===> zlib (depend)
> @ -> /«PKGBUILDDIR»/flavor-8.3-1-amd64/sys
> machine -> /«PKGBUILDDIR»/flavor-8.3-1-amd64/sys/amd64/include
> rm -f .depend
> CC='gcc-4.6' mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/«PKGBUILDDIR»/flavor-8.3-1-amd64/sys/amd64/compile/DEBCUSTOM -std=iso9899:1999   /«PKGBUILDDIR»/flavor-8.3-1-amd64/sys/modules/zlib/../../net/zlib.c
> make MACHINE_ARCH=amd64 CC=gcc-4.6 WERROR= -DWITHOUT_KERNEL_SYMBOLS	 -C flavor-8.3-1-amd64/sys/amd64/compile/DEBCUSTOM/
> gcc-4.6 -c -x assembler-with-cpp -DLOCORE -O2 -frename-registers -pipe -fno-strict-aliasing -O1  -std=c99   -nostdinc  -I. -I../../.. -I../../../contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000  -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding  ../../../amd64/amd64/locore.S
> ctfconvert -L VERSION locore.o
> ctfconvert: No such file or directory
> *** [locore.o] Error code 1
> 
> Stop in /«PKGBUILDDIR»/flavor-8.3-1-amd64/sys/amd64/compile/DEBCUSTOM.
> make: *** [build-flavor-amd64-stamp] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/10/06/kfreebsd-8_8.3-6_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.


Reply to: