Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Date: Mon, 21 Jan 2002 22:28:39 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-apps AT cygwin DOT com
Subject: gcc v3 issue -- hacky solution
Message-ID: <20020122032839.GA23746@redhat.com>
Reply-To: cygwin-apps AT cygwin DOT com
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.23.1i

If we can generate new operators for all of the builtin types that are
currently being used in setup.exe, then, if we compile everything with
-fno-exceptions (which I've just added to Makefile.in) we won't have to
worry about having a mingw version of libstdc++.a around.

It's a hack, I know, but the alternative of somehow building a mingw
version of the stdc library is not too attractive.

So, if anyone was looking for something, oh I don't know, repetitive to
do, that would be a good project, assuming that Robert agrees.

(Unfortunately, my internal Robert simulator gives this about a 30% chance of an
agreement)

cgf