Bug#791732: FTBFS with GCC 5: new symbols appeared in the symbols file
Package: modemmanager-qt
Version: 5.11.0-1
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-5
This package fails to build with GCC 5:
> sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bl460gen8-30.hlinux.usa.hp.com
...
> dh_strip --dbg-package=libkf5modemmanagerqt6-dbg
> make[2]: Leaving directory '/«PKGBUILDDIR»'
> dh_makeshlibs '-Xusr/lib/libkdeinit5_*'
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below
> dpkg-gensymbols: warning: debian/libkf5modemmanagerqt6/DEBIAN/symbols doesn't match completely debian/libkf5modemmanagerqt6.symbols
> --- debian/libkf5modemmanagerqt6.symbols (libkf5modemmanagerqt6_5.11.0-1_amd64)
> +++ dpkg-gensymbolseWZ62M 2015-07-07 21:37:56.547869390 +0000
> @@ -269,9 +269,9 @@
> _ZN12ModemManager8Notifier15serviceAppearedEv@Base 5.8.50
> _ZN12ModemManager8Notifier16staticMetaObjectE@Base 5.8.50
> _ZN12ModemManager8Notifier18serviceDisappearedEv@Base 5.8.50
> - _ZN12ModemManager8NotifierD0Ev@Base 5.8.50
> - _ZN12ModemManager8NotifierD1Ev@Base 5.8.50
> - _ZN12ModemManager8NotifierD2Ev@Base 5.8.50
> +#MISSING: 5.11.0-1# _ZN12ModemManager8NotifierD0Ev@Base 5.8.50
> +#MISSING: 5.11.0-1# _ZN12ModemManager8NotifierD1Ev@Base 5.8.50
> +#MISSING: 5.11.0-1# _ZN12ModemManager8NotifierD2Ev@Base 5.8.50
> _ZN12ModemManager8notifierEv@Base 5.8.50
> _ZN12ModemManager9Interface11qt_metacallEN11QMetaObject4CallEiPPv@Base 5.8.50
> _ZN12ModemManager9Interface11qt_metacastEPKc@Base 5.8.50
> dh_makeshlibs: failing due to earlier errors
> make[1]: *** [pre_binary_dh_makeshlibs] Error 2
> /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target 'pre_binary_dh_makeshlibs' failed
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> make: *** [debian/dhmk_binary] Error 2
> /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target 'debian/dhmk_binary' failed
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
--
Martin Michlmayr
Linux for HP Helion, Hewlett-Packard
Reply to: