Bug#780317: evince: Non matching libevdocument3-4 symbols render evince unbuiltable

Simon McVittie smcv at debian.org
Thu Mar 12 10:05:00 UTC 2015


Control: severity 780317 normal
Control: retitle 780317 FTBFS if DEB_BUILD_OPTIONS=debug: new symbols in libevdocument3-4

On 12/03/15 00:03, Sophoklis Goumas wrote:
> I've been trying to debug some issues with evince's accels file and before
> tampering with anything I just wanted to see whether evince would build as
> it had been downloaded which it didn't, reporting:
> [
> dpkg-gensymbols: warning: some new symbols appeared in the symbols
> file: see diff output below
> + ev_debug_get_debug_borders at Base 3.14.1-2
> + ev_debug_message at Base 3.14.1-2
> + ev_profiler_start at Base 3.14.1-2
> + ev_profiler_stop at Base 3.14.1-2
> ]

As far as I can see, those symbols appear if and only if you alter
the configure invocation to add --enable-debug. cdbs does this
automatically if you build with DEB_BUILD_OPTIONS=debug - is that
what you were doing?

The requirement that Debian packages must build from source is only
release-critical for the configuration that actually gets released,
which has no special DEB_BUILD_OPTIONS, so I'm downgrading this to
a normal bug.

(The right solution is probably to conditionalize the -c4 in
DEB_DH_MAKESHLIBS_ARGS so it is only used if DEB_BUILD_OPTIONS
does not contain debug.)

    S



More information about the pkg-gnome-maintainers mailing list