This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Backtrace library [1/3]
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Ian Lance Taylor <iant at google dot com>
- Cc: <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 12 Sep 2012 16:23:29 +0000
- Subject: Re: Backtrace library [1/3]
- References: <mcroblcp3ws.fsf@google.com>
On Tue, 11 Sep 2012, Ian Lance Taylor wrote:
> The configury is fairly standard. Note that libbacktrace is built as
> both a host library (to link into the compilers) and as a target library
> (to link into libgo and possibly other libraries).
Under what circumstances will the library be built for the target - only
if a relevant language such as Go is being built, or unconditionally?
If built unconditionally, will the library build OK for the target in
situations where no target headers are yet available? (For such builds of
compilers used to bootstrap libc it would be usual to use various
--disable- options to disable libraries not needed to build libc, and to
use --enable-languages=c, but if this library is used on the host side by
the compiler then the generic --disable-libbacktrace might not suffice
since that would disable the host copy, required by the compiler itself,
as well as the target copy.)
--
Joseph S. Myers
joseph@codesourcery.com