The "supposed" fix in upstream at https://github.com/eclipse/titan.core/commit/425a11165fa7b88ca36ca363fc714432e46822fb is not a fix at all for this problem.
The problem is that the entire check in Eclipse TITAN is bogus. From what I know there was one such ABI incompatibility something like 10 years ago, and TITAN continues to have this supposed workaround. I don't think many people are running 10 years old distributions. On the contrary, the "workaround" of enforcing gcc version equality is breaking lots of current-day setups again and again - with absolutely no reason. I believe you can safely link objects created by different gcc/g++ versions, with that one ancient exception that shouldn't matter anymore these days. -- - Harald Welte <lafo...@gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
