Mail Archives: djgpp/1998/11/09/13:30:32
On 8 Nov 98, at 20:02, Nate Eldredge wrote:
> Marco Talamanca wrote:
>
> > Finally, the readme from GCC281 *strongly* advise to make a change to
> > DJGPP.ENV, deleting the [gcc] and [cpp] because the path settings provided
> > there are no longer necessary. Still the DJGPP.ENV which came with
> > DJDEV202 has those sections and a loth of path settings there. What is
> > advisable to do?
>
> I seem to recall that that advice was in error, and could cause problems
> under certain circumstances. But Andris can speak authoritatively on
> that.
There is usually no more need with DJGPP ports of gcc-2.8.X and
egcs-1.1 to specify directly $DJDIR/include where to search for include
files and $DJDIR/lib for object libraries. cpp and gcc knows these
directories.
DJGPP ports of gcc versions since 2.8.0 (including also egcs-1.1)
knows where to search for include files. However there are some
things to remeber. If these directories are not specified gcc looks
for libraries, specs file and djgpp.djl at first in gcc version specific
directory and only then in $DJDIR/lib. Otherwise serach order is
oposite.
As I remeber there were problems with gcc-2.8.0 when these definitions were
removed from DJGPP.ENV. There should be no such problem with later
versions.
With DJGPP-2.02 version of specs from $DJDIR/lib should be Ok, but it
was not so with DJGPP-2.01 and gcc-2.8.1 (crtf.o were needed to get
exceptions working).
So with DJGPP 2.02 also specs and djgpp.djl from djdev202.zip should
work. However I still think that %DJDIR%/include and %DJDIR%/lib
should not be explicitly mentioened in DJGPP.ENV. However there
ususally should be no harm from them.
> Not sure about the others, and don't want to make guesses I'll regret.
> Sorry.
Andris
- Raw text -