Mail Archives: djgpp-workers/2001/08/24/03:57:16
> Date: Thu, 23 Aug 2001 20:30:48 +0300 (WET)
> From: Andris Pavenis <pavenis AT lanet DOT lv>
>
> > DJGPP_DJL := $(shell $(CROSS_GCC) $(GCC_OPT) -print-file-name=djgpp.djl)
> >
> > This asks the compiler for the full name of the linker script, but
> > since the script is called djgpp.djl, this command cannot pick
> > djgpp-x.djl which comes with the GCC distribution. That means the C++
> > programs compiled as part of the library might crash, no?
>
> djgpp.dlj from current CVS version of DJGPP of OK for gcc-3.0.1.
This doesn't help: the above command asks GCC about the _installed_
version of djgpp.djl. Unless you drop your local CVS sandpit into the
normal DJGPP tree, under %DJDIR%/src, GCC won't use the CVS version of
djgpp.djl, it will use the one from %DJDIR%/lib instead.
Since I don't use the CVS library for production, I have the CVS tree
outside the main DJGPP tree. Am I the only one?
> All should work "out of box" if one builds CVS version of DJGPP with
> gcc-3.0.1. As I said lib/djgpp.dlj from current CVS is compatible with
> gcc-3.0.1
I am thinking about users who, like me, have the CVS sandbox outside
the DJGPP tree. These users will be unable to build the CVS version
(or djlsr204.zip, for that matter) unless they replace lib/djgpp.djl.
We need to solve that, I think.
- Raw text -