On Wed, 30 Mar 2005, Philipp Thomas wrote:

Jerry Feldman [Tue, 29 Mar 2005 09:19:36 -0500]:

...

In any case I would like to know if anyone has experienced any interoperability issues with objects produced by GCC 3.2, 3.3 or 3.4

With gcc 3.4 the C++ ABI changed, see http://gcc.gnu.org/gcc-3.4/changes.html . So C++ objects compiled with 3.4 are incompatible with those created by previous versions.

Philipp

Hi. One of my questions whould be : I am using SuSE 9.3 beta3 and it uses gcc 3.3.5 (i dont know if this will change in the official release of SL9.3). So it seems that if someone builds a C++ executable in a distro using gcc 3.4, it would not be possible for me to execute it in SL9.3 right ?

On Tuesday 29 March 2005 5:33 pm, Philipp Thomas wrote:

With gcc 3.4 the C++ ABI changed, see http://gcc.gnu.org/gcc-3.4/changes.html . So C++ objects compiled with 3.4 are incompatible with those created by previous versions. I am aware of the 3.4 ABI fixes for C++, but in essence I was asking about any other issues. Hopefully our team that reported the problem will be able to reproduce it.

I am using SuSE 9.3 beta3 and it uses gcc 3.3.5 (i dont know if this will change in the official release of SL9.3). So it seems that if someone builds a C++ executable in a distro using gcc 3.4, it would not be possible for me to execute it in SL9.3 right ? Yes and no. There is a compile-time switch that you could use. One way to ensure compatibility is to compile staticly. This binds the

On Tuesday 29 March 2005 6:45 pm, Filippos Papadopoulos wrote: libraries to your code. (Not recommended). Another is to use the older C++ run-time libraries. If libstdc++ is built correctly, a 3.4 executable should run on older systems, but I have not yet verified that. -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9