Source: kjsembed
Version: 5.23.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg00007.html

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»'
> dh_strip  --dbgsym-migration='libkf5jsembed5-dbg (<= 5.19.0-1~~)'
> make[2]: Leaving directory '/«PKGBUILDDIR»'
> dh_makeshlibs '-Xusr/lib/libkdeinit5_*'  # [-a]
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libkf5jsembed5/DEBIAN/symbols doesn't match 
> completely debian/libkf5jsembed5.symbols
> --- debian/libkf5jsembed5.symbols (libkf5jsembed5_5.23.0-1_amd64)
> +++ dpkg-gensymbolsBZNHxi     2016-07-13 19:28:41.652000000 +0000
> @@ -176,7 +176,7 @@
>   _ZN8KJSEmbed9SvgWidgetC2EPN3KJS9ExecStateEP10QSvgWidget@Base 4.96.0
>   _ZNK3KJS10Identifier7qstringEv@Base 4.96.0
>   (optional=gccinternal)_ZNK3KJS7JSValue4typeEv@Base 5.19.0
> - _ZNK3KJS7JSValue8toStringEPNS_9ExecStateE@Base 5.23.0
> +#MISSING: 5.23.0-1# _ZNK3KJS7JSValue8toStringEPNS_9ExecStateE@Base 5.23.0
>   _ZNK3KJS7UString7qstringEv@Base 4.96.0
>   _ZNK3KJS8JSObject11toPrimitiveEPNS_9ExecStateENS_6JSTypeE@Base 4.96.0
>   _ZNK8KJSEmbed13ObjectBinding4typeEv@Base 4.96.0
> dh_makeshlibs: failing due to earlier errors
> make[1]: *** [pre_binary-arch_dh_makeshlibs] Error 255

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/kjsembed_5.23.0-1_unstable_gcc6.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 via email to