#include_next and removing of duplicate include dirs

[Nathan Sidwell]

Zack Weinberg wrote:
> 
> On Mon, Sep 03, 2001 at 08:01:33AM -0400, Jakub Jelinek wrote:
> > On Sun, Sep 02, 2001 at 10:14:04AM -0700, Benjamin Kosnik wrote:
> > > Jakub, I think this is because a third set of includes is also necessary,
> No.  The bug is either in the code that set COMPILER_PATH in the
> first place, or the code that is using #include_next in the first
> place.  In fact, I will bet you that neither is actually necessary.
COMPILER_PATH should be being zapped by
2001-07-01  Nathan Sidwell  <nathan@codesourcery.com>

	* tlink.c (recompile_files): Remove COMPILER_PATH and
	LIBRARY_PATH from the environment.
for this very reason. Oh, I see that's not on the 3.0 branch, mainline
only.

nathan

-- 
Dr Nathan Sidwell   ::   http://www.codesourcery.com   ::   CodeSourcery LLC
         'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org