> However, shouldn't the build of libiberty ignore the standard > include directory and use the newlib version during the build > process? I've already submitted a change to libiberty to handle this bug. I'm awaiting approval.