X-Authentication-Warning: kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f
Date: Thu, 28 Jun 2001 17:45:07 -0500
From: JT Williams <jeffw AT darwin DOT sfbr DOT org>
To: djgpp-workers AT delorie DOT com
Subject: Re: gcc 3.0 released
Message-ID: <20010628174507.A8598@kendall.sfbr.org>
Mail-Followup-To: djgpp-workers AT delorie DOT com
References: <2110-Wed27Jun2001201114+0300-eliz AT is DOT elta DOT co DOT il> <Pine DOT A41 DOT 4 DOT 05 DOT 10106281833130 DOT 20178-100000 AT ieva06 DOT lanet DOT lv>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.A41.4.05.10106281833130.20178-100000@ieva06.lanet.lv>; from pavenis@lanet.lv on Thu, Jun 28, 2001 at 06:44:58PM +0300
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

I may well be overlooking something, but from this thread
it seems that the _only_ way to get into trouble is to install
stock djdev203 *after* installing gcc-3.0 (because that would
overwrite the gcc-3.0-supplied djgpp.djl with a stale copy
from djdev203).

If this is the case, it sure seems reasonable to me to require
that djdev 2.03 be installed _prior_ to installing gcc-3.0, i.e.,
you *must* upgrade to djdev 2.03 before installing gcc-3.0.