X-Spam-Check-By: sourceware.org
Message-ID: <43FB46BB.70C04F35@dessent.net>
Date: Tue, 21 Feb 2006 08:58:35 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Octave's oct-modules built with gcc-3.4.4-1 crash octave.
References: <20060221164913 DOT 39595 DOT qmail AT web51501 DOT mail DOT yahoo DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

"James R. Phillips" wrote:

> This situation as regards gcc and octave is admittedly awkward, but I see no
> simple remedy as a package maintainer.  It would be nice if gcc 3.4 were fixed
> - but I can't make that happen.  It would be nice if cygwin supported multiple
> simultaneous gcc installs - but I can't make that happen either.  Nor can I
> easily turn off the default selection of gcc for upgrading whenever setup.exe
> is run.  All in all, the situation is annoying, but one learns to live with it.

Well, there is a patch in PR24196 against 3.4 which fixes the problem. 
It looks like the logical solution would be to include that patch in
Cygwin's gcc.  Gerrit?

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/