Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com X-Authentication-Warning: modi.xraylith.wisc.edu: khan owned process doing -bs Date: Thu, 25 Feb 1999 12:10:44 -0600 (CST) From: Mumit Khan To: Brad Porter cc: Steve Biskis , cygwin AT sourceware DOT cygnus DOT com Subject: RE: _ctype_ In-Reply-To: <604BE7100DB8D21180C900805FC772ABEC29@berlin.netdelivery> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 25 Feb 1999, Brad Porter wrote: > Sorry. I didn't intend this to be a "bug report" but more > of "what have I done wrong?" I believe it is due to having the snapshot > release, as Steve suggested. Anyway, the libstdc++.a modules that have the > undefined symbols are iostream.o and iovscanf.o Thank you! That's what I needed to know. Looks like we need to rebuild all the object modules that uses ctype etc when using the new cygwin development snapshots. The interface for ctype was changed since b20.1, so it's something that I don't see (I build everything with a stock b20.1 copy). Unfortunately, I don't a simple workaround other than rebuilding the C++ runtime library in this case. Regards, Mumit ps: I'm going to copy this to the cygwin list as well. Hopefully that's not a problem. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com