Date: Tue, 18 May 1999 13:56:21 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Andris Pavenis <pavenis AT lanet DOT lv>
cc: djgpp-workers AT delorie DOT com
Subject: Re: gcc 3.0
In-Reply-To: <Pine.A41.4.05.9905170950280.58860-100000@ieva01.lanet.lv>
Message-ID: <Pine.SUN.3.91.990518135600.24330b-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Mon, 17 May 1999, Andris Pavenis wrote:

> The problem that must be resolved is building upcomming version for DJGPP
> and I expect problems there:
> 	forcing --prefix=$DJDIR through configure
> 	scripts and makefiles, it is needed there and we cannot avoid it. 

What about building on non-LFN platforms?  Does it work?

> 	Of course we can find some hack to get environment variable
> 	resolved in other way but I don't think gcc is appropriate place
> 	where to use such hacks.

Is this something that /dev/env cannot solve?

What about -imacros in specs--does this have any relevance to the
official distribution, or is this something that is added manually to
the DJGPP binary zip?