Mail Archives: djgpp/1998/03/05/07:31:38
Hi!
> On 4 Mar 1998, Jon D. Slater wrote:
>
> > I also modified the DJGPP.ENV to reflect the new directory.
>
> Do not, reapeat: DO *NOT* edit your DJGPP.ENV! It uses arcane syntax
> which is easy to misinterpret (especially if you don't make yourself
> familiar with its description). Incorrect changes in DJGPP.ENV will most
> probably break your installation, so just don't do it.
>
I see at least one place where such editting may be needed:
the change of search paths for include files and libraries
when some new package (or updated version) is being installed
(for example djdev201.zip comes with
%DJDIR%/contrib/grx20/include in include path and
%DJDIR%/contrib/grx20/lib in lib path,
current stable version 2.2 lives in %DJDIR%/contrib/grx22,
I'm using latest available beta 2.27a and want that directory
name reflect the actual version)
The second thing user may want to change is the setting of
variable LFN to enable or disable use of long filenames by
default.
My suggestions are following:
1) If You think You really should modify DJGPP.ENV at first
make backup copy of it (or keep djdev201.zip available)
before doing any changes. It is good also if DJGPP.ENV
gets accidentally deleted.
2) If something goes wrong restore it from backup copy at first
(BEFORE ASKING ANY QUESTIONS IN THIS GROUP)
If this fixes problem You perhaps did something wrong and
it is time to think and read docs before next attempt to do the
corrections.
I think these two rules can help to solve most such misconfiguration
problems. They helped also me when I did something wrong with
this file.
About changing the other things (except the paths I mentioned)
one should seriously think is such changes are necessary. In most
situations the answer will be NO.
Andris Pavenis
- Raw text -