[Bug 70821] Re: libglibmm-2.4-dev seems to be buggy on ppc

[deadchip]

Just FWIW, and i'm sure Daniel will agree with me, it can hardly be a
BMPx error if the destructor for ustring is not known to the so lib
(Where the ctor seems to be or it would have complained about that). We
also use very conservative flags by default (only -O2 and -ggdb3, latter
only being for debugging), and recently since recent 0.33.x and 0.34.0
RCx no flags at all since Fedora Core 6, on which i develop BMPx, has a
problem with g++ and binutils which prevents BMPx from building
correctly at all with -O2 enabled, so this issue is if anything at all a
linker issue, and  was for you most likely resolved the same way it was
for me: because of the now-missing CFLAGS/CXXFLAGS. I just wanted to
annotate that because it "certainly" was "not" a bug from BMPx...

-- 
libglibmm-2.4-dev seems to be buggy on ppc
https://launchpad.net/bugs/70821