On Tue, Feb 23, 2010 at 02:02:10PM -0800, Roland McGrath wrote:
A libebl.a build is directly tied to the backends from the same
So the src/ utilities that use libebl.a directly won't be happy until
you relink them against a rebuilt libebl.a that matches the backends.
See MODVERSION on config.h and where libebl/eblopenbackend.c uses it.
We do this because libebl and the backends are not stable ABIs (or even APIs).
Only programs that are part of the elfutils build really use libebl.a directly.
I'm not providing a libebl.a in a package, so I don't have to
worry about other users of that, I just need to create more tight
depedencies between the packages I'm providing.
Thanks for the explanation.