libctf linking against different libbfd builds, but using the same soname

[Matthias Klose]

Nick,

I made a first attempt at packaging binutils trunk and libctf.  Two new shared
libraries are installed, libctf and libctf-nobfd.  libctf-nobfd is the same
library for native builds, and for builds targeting other architectures, however
the libctf builds are differing, because they link to different libbfd
libraries.  The packages for Debian/Ubuntu are built with the attached patch,
and setting BFD_SOVER_EXT to "-system" for native builds, and to
"-$(TARGET_ARCH)" for cross binutils.  Ending up now with conflicting sonames
for the native and cross libctf builds.  Now I think I should extend the patch
below to encode the same information into the libctf soname, so that I am able
to distinguish between the native and the various cross builds. Is this correct,
or can you discard the cross libctf builds and use the native build instead?

The other question I didn't look into detail yet: Does the linking of libctf
against libbfd change any of the libctf ABI?

Matthias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 135_bfd_soversion.patch
Type: text/x-patch
Size: 2016 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20191122/323dcb36/attachment.bin>