X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Authentication-Warning: kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f
Date: Sat, 1 Nov 2003 08:58:54 -0600
From: JT Williams <jeffw AT darwin DOT sfbr DOT org>
To: djgpp AT delorie DOT com
Subject: Re: Upgrading gcc compiler
Message-ID: <20031101145854.GA17632@kendall.sfbr.org>
Mail-Followup-To: djgpp AT delorie DOT com
References: <bntl5l$156u34$1 AT ID-79865 DOT news DOT uni-berlin DOT de> <3fa3a92b$0$167$cc7c7865 AT news DOT luth DOT se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3fa3a92b$0$167$cc7c7865@news.luth.se>
User-Agent: Mutt/1.4.1i
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Perhaps djgpp gurus should make a blanket policy of _always_ recommending
that users remove an existing version before upgrading?  It's simple enough
to do (e.g.,'rm -vf @manifest/gcc32b.mft'), and cheap insurance against FAQs.

If you know what you're doing, you can of course ignore the advice.

On Sat|2003.11.01, Martin Str|mberg wrote:
-: Alex Vinokur <alexvn AT bigfoot DOT com> wrote:
-: : Must one remove the version-3.2 files before unzipping?
-: 
-: Not sure about must, but you should. If you have problems the first
-: thing is to make sure you don't have a strange mix.