[Bug default/18838] Normalize the output of abidw

dodji at redhat dot com sourceware-bugzilla@sourceware.org
Thu Jan 1 00:00:00 GMT 2015


--- Comment #5 from dodji at redhat dot com ---
(In reply to andrew.c.morrow from comment #4)

> Needing to have access to two versions of libb.so is also problematic in the
> context of a build system like SCons, because there typically is no way to
> retain the prior version of libb.so, or name such a thing in the dependency
> graph.

Ah, I see.

There is a --weak-mode of abicompat, with which you just need to have access to
the later version of libb.so.  i.e:

  abicompat --weak-mode liba.so libb.so

But in that case, abicompat won't tell you if a symbol which liba.so consumes
from libb.so disappears from libb.so.  It'll just tell you if the types
consumed by liba.so from libb.so stop meaning the "same thing".

So close, and yet so far.  So yeah, I agree with you. 

There is another thing to keep in mind.  Right now, even if two versions of
libb.so have the *same* ABI, their corresponding abidw output might be

This is mainly because the output of abidw is not normalized.  Hence this
enhancement request.  Also, even when the output of abidw becomes normalized, a
new version of libabigail might make that that output slightly change, for
instance, because we add support for new ABI artifacts.

But then, that is just a missed optimization, I agree with you. For the sake of
the intellectual correctness, I thought I'd mention it nonetheless.

Thank you for following up on this.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Libabigail mailing list