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

Bug#871089: speech-tools: FTBFS: /bin/sh: 1: g++-6: not found



Source: speech-tools
Version: 1:2.4~release-5
Severity: serious
Tags: buster sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20170805 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[2]: Entering directory '/<<PKGBUILDDIR>>'
> Check system type
> Remake modincludes.inc
> 	NATIVE_AUDIO
> 		ok
> 	EDITLINE
> 		config/modules/editline.mak
> 	SIOD
> 		siod/siod.mak
> 	WAGON
> 		stats/wagon/wagon.mak
> 	SCFG
> 		grammar/scfg/scfg.mak
> 	WFST
> 		grammar/wfst/wfst.mak
> 	OLS
> 		stats/ols.mak
> 	RXP
> 		rxp/rxp.mak
> 	LINUX16_AUDIO
> 		config/modules/linux16_audio.mak
> Making in directory ./siod ...
> making dependencies -- siodeditline.c el_complete.c editline.c el_sys_unix.c slib.cc slib_core.cc slib_doc.cc slib_file.cc slib_format.cc slib_list.cc slib_math.cc slib_sys.cc slib_server.cc slib_str.cc slib_xtr.cc slib_repl.cc slib_python.cc io.cc trace.cc siod.cc siod_est.cc 
> g++-6 -fno-delete-null-pointer-checks -c -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O3 -fPIC -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O3 -fPIC -Wall -DSUPPORT_EDITLINE -I../include -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security slib.cc
> /bin/sh: 1: g++-6: not found
> ../config/rules/c.mak:59: recipe for target 'slib.o' failed
> make[3]: *** [slib.o] Error 127

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/speech-tools_2.4~release-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.


Reply to: