Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Fri, 21 Jun 2002 01:58:09 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Building a MinGW build of aspell without much luck :( Message-ID: <20020621055809.GA4028@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <000e01c218d0$50afd500$be3210ac AT sncxp> <20020621031046 DOT GE16786 AT redhat DOT com> <3D12BD05 DOT 1050909 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D12BD05.1050909@ece.gatech.edu> User-Agent: Mutt/1.3.23.1i On Fri, Jun 21, 2002 at 01:43:33AM -0400, Charles Wilson wrote: >As Earnie mentioned in the announcement for the most recent update of >the mingw-runtime and w32api packages for cygwin, libmingwex is a new >addition. > >>To use these functions, you will need to explicitly add -lmingwex to >>your command line. In future releases of GCC, libmingwex.a will >>become a system lib added automatically by specs. > >So, it's not a bug that current gcc's spec file doesn't have it; it's a >new feature of mingw-runtime that is not yet supported by our gcc. Ah, that's right, I missed this announcement. My spam filter kicked it out as spam for some reason so it never even got forwarded (by my procmail forwarder rule) to the cygwin mailing list. cgf -- 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/