Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From: "Robert McNulty Junior" <bmj2001 AT bellsouth DOT net>
To: "Max Bowsher" <maxb AT ukf DOT net>, <cygwin AT cygwin DOT com>
Subject: RE: Cygwin 1.3.19-1
Date: Fri, 24 Jan 2003 18:37:37 -0600
Message-ID: <KPEPLCKFOMHAHJPDILBPAEECCCAA.bmj2001@bellsouth.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
In-Reply-To: <033301c2c409$1cfbf7e0$78d96f83@pomello>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal

Max, I used Timidity, too. Compiled Fine.
With Gcc-3.2.2, before the changes today.
I'll go back as soon as I think about this through.
If you noticed on the gcc-3.2.2 (later on) what caused it was a couple of
missing identifiers.
JCF and another.
I'll look into either sources.


-----Original Message-----
From: Max Bowsher [mailto:maxb AT ukf DOT net]
Sent: Friday, January 24, 2003 6:32 PM
To: Robert McNulty Junior; cygwin AT cygwin DOT com
Subject: Re: Cygwin 1.3.19-1


Robert McNulty Junior wrote:
> I went back to Cygwin 1.3.18-1
> Sorry, Chris.
> It was too buggy trying to compile the GCC compilers.

Well, that is what [prev] is for - but it might be in your interest to try
to find a smaller testcase than "compile gcc-3.3 or above" !

Strange that it should say "Signal 11" - IIRC Cygwin usually says
"Segmentation fault (core dumped)"

Max.




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/