[RFC] Adding libbacktrace

[Andrew Burgess]

* Nick Clifton <nickc@redhat.com> [2021-09-10 15:34:33 +0100]:

> Hi Andrew,
> 
> > So, I can see two possible solutions here I think, one would be to
> > remove the call to configure-target from src-release.sh - surely we
> > don't expect to be building target libraries for binutils-gdb, right?
> 
> This script is so arcane that I would be hesitant to change anything...
> 
> > Or, I can try to figure out what causes the configure/build rules for
> > zlib (as a target module) to be disabled, and do the same thing for
> > libbacktrace.
> 
> My guess: zlib is in host_libs but not target_libraries, whereas libbacktrace
> is in both.

This rang a bell, so I checked, and indeed, the last time you tried to
sync the top level files from GCC to binutils-gdb the builds broke,
the reason was:

  https://sourceware.org/pipermail/binutils/2019-May/107094.html

In gcc zlib has been added to the target_libraries list.

And indeed, if I follow the same build recipe, as was reported in that
email thread, which is './configure && make all' which is different to
what I usually do, './configure && make all-{gdb,gas,bintuils,ld}'
then I see the same broken build but now with libbacktrace.

There seems to be a general problem here that our top-level Makefile
scripts will try to build target modules if they are available, even
when that's not the right thing to do for binutils-gdb.

Any ideas welcome :)

Thanks,
Andrew