Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Fri, 18 Jan 2002 14:12:54 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: gcc -mno-cygwin STL support for setup.exe? Message-ID: <20020118191254.GB28692@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20020118180305 DOT GA2312 AT dothill DOT com> <20020118180632 DOT GA24778 AT redhat DOT com> <20020118185956 DOT GC2312 AT dothill DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020118185956.GC2312@dothill.com> User-Agent: Mutt/1.3.23.1i On Fri, Jan 18, 2002 at 01:59:57PM -0500, Jason Tishler wrote: >> The biggest issue with relying on libstdc++.a for for setup.exe is that it >> requires this library to be built for cross-compilation. I have no idea how >> to do that. > >I don't know either -- this is why I'm asking for help. I think that was clear. What I'm trying to say is that it may not be possible to use functions from libstdc++.a. In gcc 3.x, this will include things like new() and delete(). cgf