[PATCH v3 00/33] CTF linking support

[Matthias Klose]

On 07.09.19 00:54, Nick Alcock wrote:
> As another change in this series, we make libctf into an installable
> (.a) library, so that external programs can benefit from the new libctf
> linking API, to link CTF like ld does.  Since libctf uses libiberty, and
> many plausible uses link libctf.a into a shared library, this also
> requires us to install the PIC version of libiberty: most distros are
> doing this already, so this is probably worth doing regardless.

Speaking for the Debian/Ubuntu builds, I'm not that keen to have to ship a 
shared libiberty library ... Why can't that be done like for libbfd and 
libopcodes, to include the convenience libiberty into the shared libaries?

The libbfd build has a nice feature to include an extra name into the library 
name, e.g. libbfd-2.32.51-system.20190821.so, or for cross builds 
libbfd-2.32.51-ppc64el.20190821.so.  It would be nice if libctf could provide a 
similar schema, assuming that libctf doesn't have a stable ABI like libbfd.

> But despite the caveats in that patch, in conjunction with a CTF-capable
> GCC,

I assume this is for GCC trunk, or are you planning to maintain a CTF branch for 
GCC 9?

Matthias