[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc-bugs
Subject:    Re: Results for 2.97 20010212 (experimental) testsuite on i686-pc -cyg win
From:       DJ Delorie <dj () redhat ! com>
Date:       2001-02-28 18:53:18
[Download RAW message or body]


> Does this look OK to you?  If so, OK to commit for branch and mainline?

OK for mainline, but you'll have to swap /usr/include and
/usr/local/include to get the same semantics as before (-idirafter
appens, -isystem prepends).  Verify this with "gcc -v ..." to make
sure the search order doesn't change.

I'm OK with it for branch if those tests passed for 2.95.  Otherwise,
you'll probably need a higher authority than I to OK it.

> > I have a solution to this problem.  It may even be correct.
> > 
> > The cause of the problem is using "-idirafter /usr/include" rather than
> > "-isystem /usr/include".  This is fixed with the following patch, which
> > bootstraps on the gcc-3.0 branch and eliminates the cpp testsuite failures.
> > 
> > --- gcc/config/i386/cygwin.h.orig	Tue Feb  6 21:11:08 2001
> > +++ gcc/config/i386/cygwin.h	Tue Feb 27 20:08:33 2001
> > @@ -88,7 +88,7 @@
> >  #define MINGW_LIBS "-L" CYGWIN_CROSS_DIR "/lib/mingw"
> >  #define MINGW_INCLUDES "-I" CYGWIN_CROSS_DIR "/include/mingw"
> >  #else
> > -#define CYGWIN_INCLUDES "-isystem /usr/local/include -idirafter
> > /usr/include"
> > +#define CYGWIN_INCLUDES "-isystem /usr/local/include -isystem /usr/include"
> >  #define CYGWIN_W32API "-I/usr/include/w32api"
> >  #define CYGWIN_LIB "/usr/lib"
> >  #define MINGW_LIBS "-L/usr/local/lib/mingw -L/usr/lib/mingw"
> > 
> > I don't understand why -idirafter was used.  There are only a few
> > occurrences of it in the source tree. If it wrong for cygwin it may be wrong
> > elsewhere as well.
> > 
> > Your thoughts?
> 

[prev in list] [next in list] [prev in thread] [next in thread]