From:	pavenis AT lanet DOT lv
Message-ID:	<B0000099319@stargate.astr.lu.lv>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date:	Wed, 25 Aug 1999 14:39:25 +0300
MIME-Version:	1.0
Subject:	Re: new GCC port
References:	<B0000099315 AT stargate DOT astr DOT lu DOT lv>
In-reply-to:	<Pine.SUN.3.91.990825141523.2834b-100000@is>
X-mailer:	Pegasus Mail for Win32 (v3.12a)
Reply-To:	djgpp-workers AT delorie DOT com

On 25 Aug 99, at 14:19, Eli Zaretskii wrote:

> 
> 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.
> 

I think using environment variable TOP in dxegen.c can be dangerous 
if somebody will use it due to some other reason. As result that can 
break DXEGEN.EXE in some conditions.

Therefore my suggestion is to leave $DJDIR/lib in LD command line 
and to specify ../../lib explicitly in dxegen.exe command line (of course 
it should be searched before $DJDIR/lib so it must appear earlier in LD 
command line).

Andris

- Raw text -