Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-Id: <199907180101.UAA07441@mercury.xraylith.wisc.edu>
To: John Fortin <fortinj AT ibm DOT net>
cc: "cygwin-developers AT sourceware DOT cygnus DOT com" <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject: Re: _ctype_ not exported by cygwin1.dll ?? 
In-Reply-To: Your message of "Sat, 17 Jul 1999 21:43:16 EDT."
             <37913134 DOT A9C060A9 AT ibm DOT net> 
Date: Sat, 17 Jul 1999 20:01:13 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

John Fortin <fortinj AT ibm DOT net> writes:
> Mumit,
> 	They worked fine....

Whew.

> 
> 	Question.. If I wanted to build gcc 2.95, which snapshot should I use,
> and does ir include the patches at your ftp site.
> 

Get the latest snapshot from ftp://egcs.cygnus.com/pub/egcs/snapshots/,
apply my patch (there is a "combined" patch file in the tarball in 
addition to all the individual patches), and just build.
  
  $ mkdir objdir
  $ cd objdir
  $ CONFIG_SHELL=bash <srcdir>/configure -v \
    --prefix=/Cygnus/cygwin-b20 \
    --exec-prefix=/Cygnus/cygwin-b20/H-i586-cygwin32 \
    i586-cygwin32
  $ make bootstrap

Now here're the tricky parts:
  
  1. your prefix etc may be different 
  2. make bootstrap will likely fail due to compare mismatch. Don't know
     why that happens, but since the testsuite does fine, I'm not going
     to worry about it now. This is what I do:
     
     $ make 
     $ make install
     [add the new one to path]
     $ make clean
     $ make 
     $ make install

Of course, it's much easier if you do it all on a Linux box ;-)

Good luck.

Regards,
Mumit