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
Message-Id:	<199906210350.WAA08862@mercury.xraylith.wisc.edu>
To:	zaimi AT kiwi DOT iamp DOT tohoku DOT ac DOT jp
cc:	cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: _ctype_ again (long)
In-Reply-To:	Your message of "Mon, 21 Jun 1999 05:16:57 -0000."
	<376DBCB8 DOT CC396176 AT kiwi DOT iamp DOT tohoku DOT ac DOT jp>
Date:	Sun, 20 Jun 1999 22:50:27 -0500
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Samy Alex ZAIMI <zaimi AT kiwi DOT iamp DOT tohoku DOT ac DOT jp> writes:
> Hello,
> I have a problem with _ctype_. This problem was
> already described early this year on this list,
> but since then new versions of compilers appeared,
> so I need some updates for possible solutions.
> So, here is my story :
> 1. I have installed cygwin-20.1 from december
> 1998,
> 2. I have installed the 15Jan99-cygwin1.dll
> snapshot only,
> 3. I have installed Mumit's egcs v1.1.2, from
> 17.03.99 (also known as 2.91.66),

Ah, this has been discussed quite a few times already. The dev
snapshots have different representations for certain types such
as those in <ctype.h> etc, and you need to rebuild *all*
libraries that use <ctype.h> etc with the new dev headers. In
this particular case, it means that you'll have to rebuild the
runtime libraries. I don't remember off-hand the use what else
will necessitate a rebuild. 

The next cygwin is not supposed to break binary compatibility of
existing binaries, but it'll surely break binary compatibility at
the object level (ie., you'll have to rebuild quite a bit of 
existing objects code). For beta software like Cygwin, this is 
quite reasonable and to be expected IMO.

Regards,
Mumit


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

- Raw text -