On Mon, 1 Mar 2010, Andreas Schwab wrote: > Jack Howarth <howa...@bromo.med.uc.edu> writes: > > > While looking at PR42308 and trying to understand why the make check > > is leaky and starts to call the system compiler instead of the xgcc during > > a make check on either x86_64-apple-darwin9 or i686-apple-darwin10, I > > noticed > > that we seem to build libiberty both at the toplevel and within the multilib > > subdirectories (x86_64-apple-darwin9 and i686-apple-darwin10 respectively). > > Is this expected behavior as I don't see anything other than libiberty > > duplicated in this fashion? > > The toplevel libiberty is the host library, the others are the target > libraries. There is another one in the build-$build directory which is > the build library.
But I've previously noted that target libiberty seems completely useless; libstdc++-v3 uses a demangler source file but the target libiberty.a (with a mixture of licenses some of which are unsuitable for target library code) doesn't get used as far as I can tell. -- Joseph S. Myers jos...@codesourcery.com
