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? I am wondering if this duplication of the
libiberty build might have something to do with the inappropriate CC
assignment during a toplevel 'make -k check' for these two targets.
Any advice for trying to pin down the origin of this testsuite harness
bug would be most appreciated.
Jack
