Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sat, 28 Apr 2001 12:15:48 -0400 From: Christopher Faylor To: Cygwin Subject: Re: Fw: [ANNOUNCEMENT] Updated: gcc 2.95.3-4, binutils 20010425-1 Message-ID: <20010428121548.H14298@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: Cygwin References: <001b01c0cfae$42fb52c0$c4332041@campbell> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <001b01c0cfae$42fb52c0$c4332041@campbell>; from DaleCampbell@revolutionist.com on Sat, Apr 28, 2001 at 02:41:31AM -0400 On Sat, Apr 28, 2001 at 02:41:31AM -0400, Christopher Dale Campbell wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >I think he actually meant to reply to the list, instead of just me. >However, I've seen questions regarding the upgrade not working, but I >haven't seen any answers. Noted in another e-mail, is it possible >just to downgrade until the problems (if they exist) are fixed? gcc is working fine for me, so there is little hope that this alleged gcc problem will be fixed. So, go ahead and back down to B20.1. You'll probably want to have some kind of plan in place for bouncing back to B20.1 after each setup.exe run, since if no one can debug this problem it will still be in 1.3.2, 1.3.3, 1.3.4, 1.3.5, etc. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple