Hi, On 2014-09-11 12:22, Paul Wise wrote:
I am rebuilding poppler for wheezy-backports. My normal build process includes DPKG_GENSYMBOLS_CHECK_LEVEL=4
That isn't a wise thing to do, with a different toolchain.
and as a result I got a build failure (see below) due to new symbols being introduced. Based on the name these are clearly private symbols that should not be exported in the public ABI, please set the default symbol visibility to hidden.
libpoppler-qt4-N (and now libpoppler-qt5-N) already *do* have symbols visibility by default, and this is a Debian-specific change (just because I haven't found the time to do the proper buildsystem bits upstream). What you see are internal symbols which older GCCs somehow still export. I cannot do anything about them, and if you see the symbols file for libpoppler-qt4-3 (in stable), these symbols are there, just marked as optional (as gccinternal stuff). In the end: a) there is nothing I can do about them b) don't use DPKG_GENSYMBOLS_CHECK_LEVEL=4 with a different toolchain -- Pino Toscano -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
