On Wed, Sep 12, 2012 at 9:23 AM, Joseph S. Myers <jos...@codesourcery.com> wrote: > 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?
My intent is to only build it when something needs it, e.g., libgo. I don't know if I've expressed that intent correctly. > 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.) The library does currently assume that a few header files are available, so building it would presumably break in this scenario. We could introduce --disable-target-libbacktrace easily enough. Ian
