Hi Sean, Paul, >> I think you should use a suffix other than -dbg because people expect >> -dbg to be detached debugging symbols. > > I would go with either -dbg (slight preference) or -debug.
Thanks for the advice! Since -dbg is expected to carry a different content by so many people, I would go for "-debug" as an alternative. > The most recent version of libwxgtk*-dbg in Debian is just detached > debugging symbols i.e. the same as the *-dbgsym. The "-b extra runtime > checks" package has been dropped: see #655251. Thanks Sean, I went through the thread and that encouraged me to switch the "debug version libraries" to something different than "-dbg". By the way, my mentor finally answered and will *try* to upload the latest 1.4.0 version, but he is so swamped that it would be a good idea anyway to find someone else who is willing to help / mentoring this package... > It was already updated to sid :( Could you confirm that it succeeds for > you on a 32-bit machine, please? I don't have access to a 64-bit > machine for testing. I successfully cross-compiled it in sid for i386 from amd64, and today I installed a 32-bit VirtualBox image just to be sure, and the CMake error you mentioned does not show up there neither!! I can't explain it... it would be great if you could try just updating sid and rebuilding and it worked, but if keeps failing, the only difference I see in our configurations is the usage of ccache. Best, Jose Luis