On Sun, Nov 03, 2013 at 10:47:16AM +0100, Mark Wielaard wrote:
> On Sun, Nov 03, 2013 at 02:58:54AM +0100, Kurt Roeckx wrote:
> > On Sat, Nov 02, 2013 at 10:06:20PM +0100, Mark Wielaard wrote:
> > > Although the public ABI of libelf is stable and should never break,
> > > the elfutils tools (at least readelf) also use some internals from
> > > libelf, which isn't public ABI/API. So the elfutils tools (if
> > > packaged separately from libelf) should depend on the exact same
> > > version of the elfutils libelf library being installed.
> > > 
> > > The same holds true for libdw/libasm if packaged separately.
> > > They always have to be upgraded in lockstep. Other packages that only
> > > use the public interfaces of libelf (or libdw/libasm) can use whatever
> > > version that provides the public symbols they are providing.
> > 
> > I'm not sure which symbols from libelf are exported but not public
> > then.
> 
> The elfutils tools and libraries depent on some internal datastructures
> which aren't exported. They use internal headers like libelf/libelfP.h
> which normally aren't (and shouldn't be) accessible outside elfutils
> sources.

That file actually hasn't changed between those version, and I
still fail to see how it can have any effect.  The libelf.so.1
file only has the public symbols.  Any version of those symbols
should work.

The problem actually seems to be that I removed the configure
option --enable-thread-safety.  Not sure how exactly this has
an effect yet.

> If you package libasm separately it does depend on backend internals
> so should depend on the exact version of libdw1 (in which the libebl
> backends are).

I don't have a Depends for that now since I didn't know it used
the backends and it's not using anything from libdw1.  The only
thing using it in Debian also seems to be elfutils itself which
already Depends on the proper version of libdw1.  But I'll add
a Depends in libasm1 for it too.


Kurt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to