Date: Mon, 26 Jan 1998 18:54:27 -0800 (PST)
Message-Id: <199801270254.SAA29245@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: RHIDE linker problems - HELP!
Cc: Robert Hoehne <robert DOT hoehne AT gmx DOT net>, djgpp AT delorie DOT com
Precedence: bulk

At 01:24  1/26/1998 +0200, Eli Zaretskii wrote:
>
>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.
Sounds good to me, although IMHO it should also refer the user to README.1ST.

Nate Eldredge
eldredge AT ap DOT net