[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: C++ ABI change -- freezing unstable for new C++ library packages

On Tue, Jun 14, 2005 at 09:34:31PM +0200, Josselin Mouette wrote:
> Le jeudi 09 juin 2005 à 02:13 +0200, Matthias Klose a écrit :
> > For etch we will update the toolchain (glibc, binutils,
> > linux-kernel-headers, gcc) again.  Some updates look easy, other will
> > have a bigger impact on packages.  One aspect of the toolchain update
> > is the change of the C++ ABI from version 1 (102) to version 2 (1002)
> > of the GNU C++ compiler.  Looks painful, but doable, as some of you
> > may still remember the toolchain update in the early sarge stages.  In
> > short, we will have to rename all packages containing shared libraries
> > written in C++.  After these library packages have been renamed, all
> > libraries and applications depending on the changed library names have
> > to be uploaded again.  To minimize the uploads and and lower the load
> > of the buildds, C++ code should be uploaded, after the C++ compiler
> > (c++, g++) points to a compiler version providing the new C++ ABI.

> I maintain a package (hdf5) which contains a pure C library and a C++
> interface. However, I'm pretty sure the C++ library isn't used by
> packages depending on it. In this case, is it necessary for the library
> to be renamed?

If the C++ library is exposed in the package's shlibs, yes...

Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature

Reply to: