OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

configure.in (FLAGS_FOR_TARGET): Use -nostdinc even for Canadian crosses...

Browse Source 
* configure.in (FLAGS_FOR_TARGET): Use -nostdinc even for Canadian
crosses, but add gcc/include to the header search path for them.

From-SVN: r36113
This commit is contained in:
Alexandre Oliva 2000-09-02 07:18:09 +00:00 committed by Alexandre Oliva
parent 802a818185
commit afd7db2554
2 changed files with 25 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
2000-08-30 Alexandre Oliva <aoliva@redhat.com>, DJ Delorie <dj@redhat.com>
* configure.in (FLAGS_FOR_TARGET): Use -nostdinc even for Canadian
crosses, but add gcc/include to the header search path for them.
2000-08-04 David E. O'Brien <obrien@FreeBSD.org>
* MAINTAINERS: Add self to Write After Approval list.

24
configure.in
View File

@ -1244,11 +1244,27 @@ case " $skipdirs " in
FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -L$$r/$(TARGET_SUBDIR)/winsup -L$$r/$(TARGET_SUBDIR)/winsup/cygwin -L$$r/$(TARGET_SUBDIR)/winsup/w32api/lib -isystem $$s/winsup/include -isystem $$s/winsup/cygwin/include -isystem $$s/winsup/w32api/include -isystem $$s/newlib/libc/sys/cygwin -isystem $$s/newlib/libc/sys/cygwin32' ;;
esac
# If we're using a pre-built compiler (which is the case for
# Canadian crosses or when gcc isn't being built), don't discard
# standard headers.
if test "${build}" = "${host}" && test -d ${topsrcdir}/gcc; then
# If we're not building GCC, don't discard standard headers.
if test -d ${topsrcdir}/gcc; then
FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -nostdinc'
if test "${build}" != "${host}"; then
# On Canadian crosses, CC_FOR_TARGET will have already been set
# by `configure', so we won't have an opportunity to add -Bgcc/
# to it. This is right: we don't want to search that directory
# for binaries, but we want the header files in there, so add
# them explicitly.
FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -isystem $$r/gcc/include'
# Someone might think of using the pre-installed headers on
# Canadian crosses, in case the installed compiler is not fully
# compatible with the compiler being built. In this case, it
# would be better to flag an error than risking having
# incompatible object files being constructed. We can't
# guarantee that an error will be flagged, but let's hope the
# compiler will do it, when presented with incompatible header
# files.
fi
fi
# If we're building newlib, use its generic headers last, but search