Re: libiberty patch - configure/makefile for cygwin

[DJ Delorie <dj at delorie dot com>]

> Ah.  That's the key point I was missing.  I didn't even know cygwin
> could be built independently of GCC, but then again I can't think of
> a fundamental reason why that wouldn't work either.

Cygwin is almost *always* built without gcc.  The only time they're
built together is during Red Hat's internal everthing builds.

> So ultimately, after Alexandre's recent hackery, what is the right
> thing to do to get cygwin builds working again independently of gcc?

This patch should mean "if we're also building gcc, and it's a gcc
that will run on the build machine, we want to use its includes
instead of the system's default includes".  Right?

Otherwise, the target libiberty's Makefile now includes -I's for
newlib, so that's fixed.

diff -p -3 -r1.19 configure.in
*** configure.in        2000/08/02 18:56:20     1.19
--- configure.in        2000/08/04 20:32:21
*************** case " $skipdirs " in
*** 1240,1246 ****
     # 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
       FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -nostdinc'
     fi
  
--- 1240,1246 ----
     # 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
       FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -nostdinc'
     fi