On Thu, Jul 08, 2004 at 08:19:04PM +0200, Andreas Jochens wrote: > On 04-Jul-08 18:48, Colin Watson wrote: > > The rest of Debian probably won't be doing this for sarge. The C++ ABI > > transition is difficult and requires library package renaming; I > > recommend staying with g++ 3.3, even if it's a little painful. > > Is there really a C++ ABI change from gcc-3.3 to gcc-3.4? > > I just read http://gcc.gnu.org/gcc-3.4/changes.html and there seems > to be only a very small ABI change for MIPS and SPARC > which affects functions with aggregate parameters, i.e struct or > union parameters (_not_ pointers to structs or unions). I do not know > many libraries which have such functions (e.g. 'void f(struct s x)'). > > Please point me to the relevant documents which describe in which way > the C++ ABI has changed in gcc-3.4.
I don't know if there is an actual ABI change but what it accepts is more strict so it could break building packages, whether it breaks binary compatibility though is another question. Chris
signature.asc
Description: Digital signature
