qwang's finding in Comment #10 turned out to happen with GTK_IM_MODULE=xim too,
so it is unlikely related to this C++ compat issue.
> Jakub, upstream told me that this symbol conflict problem will go away
> once everyone is using libstdc++ >= 4.0. Is that correct?
Isn't it overly optimistic to think that the C++ ABI will never change again? I
also don't like the idea of abandoning compatibility with all apps compiled with
an older C++ compiler.
qwang's finding in Comment #10 turned out to happen with GTK_IM_MODULE=xim too,
so it is unlikely related to this C++ compat issue.
> Jakub, upstream told me that this symbol conflict problem will go away
> once everyone is using libstdc++ >= 4.0. Is that correct?
Isn't it overly optimistic to think that the C++ ABI will never change again? I
also don't like the idea of abandoning compatibility with all apps compiled with
an older C++ compiler.