Date: Mon, 26 Jan 1998 13:24:11 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Nate Eldredge <eldredge AT ap DOT net>
cc: Robert Hoehne <robert DOT hoehne AT gmx DOT net>, djgpp AT delorie DOT com
Subject: Re: RHIDE linker problems - HELP!
In-Reply-To: <199801260623.WAA01754@adit.ap.net>
Message-ID: <Pine.SUN.3.91.980126131810.9634A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Sun, 25 Jan 1998, Nate Eldredge wrote:

> I'm just trying to think of ways to cut down on the flood of "Cannot find
> stdio.h. What!?!" postings from people too lazy to read documentation.

I agree that it would be swell if GCC would print an explicit warning 
about these cases, I just think its implementation is not as trivial as 
it seems to be.  We need a solution that would not break the flexibility 
built into GCC as to how it is configured.  This should include the cases 
where everything GCC needs is in the current directory, for example.

How about printing a warning (which doesn't prevent attempt on 
compilation) along the following lines:

  Warning: default directories not found and DJDIR variable is not set!

Such a warning should be printed when GCC has failed to stat the default 
built-in paths and didn't find $DJDIR to be defined.