Date:	Mon, 24 Jan 2000 10:18:40 +0200 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: make depend
In-Reply-To:	<Pine.SUN.3.91.1000123094413.26609C@is>
Message-ID:	<Pine.A41.4.05.10001241001590.112552-100000@ieva01.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 23 Jan 2000, Eli Zaretskii wrote:

> 
> On Fri, 21 Jan 2000, Andris Pavenis wrote:
> 
> > If we'll put djgpp.ver in the same directory where xgcc.exe is
> > located it should work better
> 
> I don't see anything wrong with having that file in any directory
> under %DJDIR%.
> 
> But I don't understand what does ``where xgcc.exe is located'' means.
> There's no xgcc.exe in the binary distribution, AFAIK xgcc exists only
> while GCC is being built.  So in what directory should we put this
> file for the best results?

We'll perhaps I said it rather unclear. xgcc is newly built copy of gcc at
build time (to avoid confusion with old gcc). And if we are using 
'-imacros %sdjgpp.ver' hack already in building specs then it should work
at build time. I had problems with gcc-2.96 snapshots and earlier hack.


> 
> > About name: I think it's better to avoid using extension .h there.
> > 	What name do You suggest?
> 
> If there are good reasons to avoid a .h extension, then I don't have
> anything against djgpp.ver.  Why do you suggest to avoid the .h
> extension?

It's not in ordinary directory where include files are searched. So I
don't think we should name it like include file. 

> 
> > Also with time we could add it to DJDEV (lib/djgpp.ver)
> 
> That's what I had in mind.  Perhaps we will need to update djdev203
> anyway (see the problems with djgpp.djl), in which case I'd like to
> add this file there already.  Do you see any reasons why this might be
> a bad idea?
> 

Perhaps I'll install it in lib/gcc-lib/djgpp/$version anyway. djgpp.ver
should be created before xgcc.exe is used first time so it should be added
to make macro EXTRA_PASSES (see. description in gcc/Makefile.in). As
result it's being installed in the same directory where cc1.exe, cpp.exe
etc goes. Only reason why to have it in $DJDIR/lib is to make it removal
from dependencies more easy. Perhaps I can move it and place it in
$DJDIR/lib myself (in gcc295Xb.zip). I don't think it should cause
problems.

Andris

- Raw text -