Message-ID: <359B7300.696791EC@gmx.net>
Date: Thu, 02 Jul 1998 11:46:08 +0000
From: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Organization: none provided
MIME-Version: 1.0
To: Bill Currie <bill AT taniwha DOT tssc DOT co DOT nz>
CC: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
        Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>,
        Andris Pavenis <pavenis AT lanet DOT lv>,
        djgpp workers list <djgpp-workers AT delorie DOT com>
Subject: Re: Some notes about DJDEV202.ZIP
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980701110656 DOT 12487D-100000 AT is> <359A07F3 DOT 6E49F4C4 AT taniwha DOT tssc DOT co DOT nz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Bill Currie wrote :
> 
> What about telling gcc to search in $DJDIR/{include,lib} instead of
> /usr/{include,lib}?  This would make djgpp operation (IMHO) VERY
> standard even if slighly skew-wiff.  Heck, isn't $DJDIR effectivly /usr
> anyway?  It's got bin, include, src, tmp and lib haning off it and
> contrib is sort of like /usr/local.

Please excuse my question, but have you ever tried gcc 2.8x??
There is this already implemented!! You can run gcc there without
setting any paths to the default DJGPP directories (except contrib/...)

All that discussion here comes from the fact, that gcc 2.8x
is much better in handling the default DJGPP directories and
only the gcc 2.7x users will need the settings of default
search paths.

Robert