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
Date:	Mon, 15 Dec 2003 16:04:14 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: vtable with snapshot >=20031123
Message-ID:	<20031215210413.GA26554@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3FDA6322 DOT 3060100 AT gmx DOT de>
Mime-Version:	1.0
In-Reply-To:	<3FDA6322.3060100@gmx.de>
User-Agent:	Mutt/1.4.1i
Note-from-DJ:	This may be spam

On Fri, Dec 12, 2003 at 06:53:54PM -0600, Axel Naumann wrote:
>Hi,
>
>I ran into a problem with gcc 3.3.1, cygwin snapshots>=20031123 (at 
>least, probably also earlier versions).

Like 1.5.5, for instance.  This isn't specifically a cygwin snapshot
issue.

>This did not happen with earlier versions of cygwin (1.4*); as far as I 
>can remember even gcc 3.3.1 with cygwin 1.4* worked. This is why I 
>believe it's a cygwin problem, not a gcc problem - but I'm really just 
>guessing.

1) There was no cygwin 1.4*.  2) gcc 3.3.1 was released after cygwin 1.5.x.
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam AT sourceware DOT org
and be permanently blocked from mailing lists at sources.redhat.com

--
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/

- Raw text -