[RFC] Adding libbacktrace

Andrew Burgess andrew.burgess@embecosm.com
Tue Sep 14 07:46:53 GMT 2021


* Ian Lance Taylor <iant@google.com> [2021-09-13 09:53:36 -0700]:

> On Mon, Sep 13, 2021 at 3:46 AM Nick Clifton via Binutils
> <binutils@sourceware.org> wrote:
> >
> > Hi Andrew,
> >
> > > 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 :)
> >
> > Punt to gcc. :-)
> >
> > More specifically, since gcc owns the so called "master" version of
> > the configure script, they should be the ones to fix this problem.
> >
> > But I suspect that fixing this might not be at the top of their priority
> > list, but if you appeal to Ian Lance Taylor directly ypu may get a better
> > response.
> 
> For GCC it's necessary for libbacktrace to be both a host module (for
> use in gcc itself) and a target module (for use in libgo and
> libgfortran).  For binutils/gdb, I don't see any reason for it to be a
> target module.  In fact, it's not immediately obvious to me that
> binutils/gdb needs any target modules at all.  So perhaps the
> binutils/gdb configury should be tweaked to ignore target modules.
> Maybe.
> 
> In any case I don't think there is anything to change in libbacktrace
> itself, this is all a question of how the configury chooses to build
> libbacktrace.

Ian,

Thanks for your feedback.  I'm testing a configure.ac patch along the
lines you suggest.  I'll post it to the gcc list once I've finished
testing here.

Thanks,
Andrew


More information about the Binutils mailing list