[devel] symbols into dependencies

[Alexey Tourbin]

On Mon, Nov 16, 2009 at 03:01:03PM +0300, Damir Shayhutdinov wrote:
> > On the other hand, we can simply assume that symbols should not be moved
> > across the libraries.  The worst thing that can happen then (if a symbol
> > does move) is that we need to rebuild a bunch of packages, only to
> > relink their binaries and update dependencies.
> >
> > However, note that, as per tgetent, the binaries are actually going to
> > change upon relinking.  This indicates that the ABI has changed, too.
> > So the rebuild is not completely useless.
> 
> Have you thought about C++ libraries and their mangling? And the fact
> that many of C++ exported symbols in such libraries are not, in fact,
> the part of the API, they are only exported because C++ cannot control
> their visibility on the ELF symbol level. I'm talking about private
> methods of classes.

I don't get what you're trying to say, sorry.
There is nothing special about C++.

> Or C++ libraries aren't worthy enough to consider?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.altlinux.org/pipermail/devel/attachments/20091116/dfee29b4/attachment.bin>