A cross-compiler configured with (for example)
.../configure --target=arm-elf --with-headers=.../newlib/libc/include
--with-newlib
No-longer builds on some host systems because fixincludes is now scanning
/usr/include rather than the headers specified.
I suspect this is related to the sysroot change.
Here's the relevant bit of the boot log:
(TARGET_MACHINE='arm-unknown-elf'; srcdir=`cd /home/rearnsha/gnusrc/egcs-cross/g
cc; ${PWDCMD-pwd}`; \
SHELL='/bin/sh'; MACRO_LIST=`${PWDCMD-pwd}`/macro_list ; \
export TARGET_MACHINE srcdir SHELL MACRO_LIST && \
cd ../build-i686-pc-linux-gnu/fixincludes && \
/bin/sh ./fixinc.sh ../../gcc/include \
)
Fixing headers into /work/rearnsha/gnu/egcs/gcc/include for arm-unknown-elf targ
et
No forbidden identifiers defined by this target
Finding directories and links to directories
Searching /usr/include/.
Searching /usr/include/./DPS
Searching /usr/include/./X11
Searching /usr/include/./libpng
--
Summary: Fixincludes on cross-build is scanning /usr/include
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Keywords: build
Severity: critical
Priority: P2
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rearnsha at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org,mark at codesourcery dot
com
GCC host triplet: i386-netbsdelf2.0
GCC target triplet: arm-eabi arm-elf
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23131
