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 11:54:55 -0600 (CST)
From:	Mumit Khan <khan AT xraylith DOT wisc DOT edu>
To:	Steve Biskis <mlx AT san DOT rr DOT com>
cc:	Brad Porter <bporter AT NETdelivery DOT com>,
	"'Cygwin'" <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: _ctype_
In-Reply-To:	<005d01be60df$31354220$080216c0@newt.san.rr.com>
Message-ID:	<Pine.SUN.3.93.990225114938.7845F-100000@modi.xraylith.wisc.edu>
MIME-Version:	1.0

On Thu, 25 Feb 1999, Steve Biskis wrote:

> Yes, I had the same problem.  It has something to do with differences
> between the b20.1 December release and later snapshots.
> 
> I was building the Jan-15 newlib/winsup snapshot and egcs-1.1.1 OK
> but then ran into undefined reference to _ctype blah blah when trying
> to compile my stuff with the resulting tools.

It typically implies that some source module is using ctype *without*
including <ctype.h>. If someone can mail me the name of che module where
the undefined reference is coming from, I can take a look. Until then,
I'll simply ignore these messages just like I ignore hundreds of other
incomplete "bug reports" ;-)

> I was also building the Dec Cygnus release and egcs-1.1.1 and then got
> undefined reference to __imp_ctype blah blah when building my stuff.

This could be due to an oldver version of newlib which didn't export the
ctype symbols.

This is the life with snapshots. These are distributed so folks like us
can report and possibly fix problems. However, if we can't fix it, we 
also have to assume the responsibility of reporting these in a way that 
helps the maintainers to track it down.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -