Date:	Wed, 25 Aug 1999 14:19:58 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	pavenis AT lanet DOT lv
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: new GCC port
In-Reply-To:	<B0000099315@stargate.astr.lu.lv>
Message-ID:	<Pine.SUN.3.91.990825141523.2834b-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 25 Aug 1999 pavenis AT lanet DOT lv wrote:

> I think we should expect something like:
> 
> ld -X -S -r -o dxe__tmp.o -L../.././lib src/emu387.o id_emu.o src/emudummy.o 
> -Ld:/djgpp/lib d:/djgpp/lib/gcc-lib/djgpp/2.951/libgcc.a -lc d:/djgpp/lib/gcc-lib/djgp
> p/2.951/libgcc.a  -T dxe.ld
> 
> ($DJDIR/lib should always be added after paths specified explicitly)

I don't think so.  The djdev build process should always use the 
libraries created from the djlsr sources of the same release, whereas 
DJDIR might point to a previous version.  The only case that is 
different is libgcc.a, which isn't built as part of djdev.  That is why 
libgcc.a is mentioned with an explicit pathname.

If there are specific reasons that $DJDIR/lib should be used when 
building djdev, please describe them.

- Raw text -