Mail Archives: djgpp-workers/1998/07/01/04:08:00
On Tue, 30 Jun 1998, Nate Eldredge wrote:
> This is probably pure evil, but we could go back to the old directory
> tree scheme, where all libraries are in $DJDIR/lib, all includes in
> $DJDIR/include, and abandon the special GCC tree.
Let's not jump to extremes, shall we? The version-specific tree *is*
the way GCC is supposed to work, and IMHO it's A Good Thing to follow
that scheme. C_INCLUDE_PATH, LIBRARY_PATH and their ilk are there for
the users to add non-standard directories, but the standard diectories
should be found without any environment variables.
Let's keep this problem in a perspective: it only matters because many
people still use gcc 2.7.2. Otherwise, we could simply eliminate the
above variables from djgpp.env and everything would work just fine.
If we cannot find an acceptable solution that leaves everybody happy,
I would rather suggest to officially announce that v2.02 doesn't
support gcc versions prior to 2.8.1, and that whoever wants to use the
older versions will need to edit djgpp.env.
But I still think that adding %DJDIR%/lib/gcc-lib/2.81/ to
C_INCLUDE_PATH etc. would be an okay solution for the time being.
Until now, only Andris replied to that suggestion (he said he's
against it). Would others please tell what they think?
> (I suppose that makes
> trouble for those who want multiple versions of GCC installed together,
> but as Eli says, they'll have to hack DJGPP.ENV anyway.)
With the new scheme, there's less hacking that's necessary.
- Raw text -