Sender: bill AT taniwha DOT tssc DOT co DOT nz Message-ID: <359B7286.9BFF0483@taniwha.tssc.co.nz> Date: Thu, 02 Jul 1998 23:44:07 +1200 From: Bill Currie MIME-Version: 1.0 To: Robert Hoehne CC: Eli Zaretskii , Hans-Bernhard Broeker , Andris Pavenis , djgpp workers list Subject: Re: Some notes about DJDEV202.ZIP References: <359A07F3 DOT 6E49F4C4 AT taniwha DOT tssc DOT co DOT nz> <359B7300 DOT 696791EC AT gmx DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Precedence: bulk Robert Hoehne wrote: > 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/...) Fair enough!! I haven't used DJGPP since December (nor DOS much for that matter). So, no, I haven't tried 2.8x on DJGPP (but I did port it to the big-endian i860:) > 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. Umm, then just what is the problem? if 2.8 looks in the right places (with $DJDIR/* coming after the version dependent dirs, and 2.7x only looks in $DJDIR/*, then I can't see any room for incompatabilities. Hmm, just had a look back and the problem seems to be if $DJDIR/* is in djgpp.env. Ach, the only solutions I can see (probably unacceptable) are either for 2.8x to ignore LIBRARY_PATH and C_INCLUDE_PATH, or strip $DJDIR/* out of them. Both seem kind of bletch. Bill -- Leave others their otherness.