Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <3948728C.3FE7AEF5@ece.gatech.edu>
Date: Thu, 15 Jun 2000 02:07:08 -0400
From: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Problem compiling perl module Term::ReadKey under cygwin
References: <3947B531 DOT D14BF8DD AT adaptivesilicon DOT com> <3947BBE9 DOT 5B33C61E AT ece DOT gatech DOT edu> <03ec01bfd678$b2fce140$032c1818 AT rochester DOT rr DOT com> <39486436 DOT AC1519E6 AT ece DOT gatech DOT edu> <20000615015950 DOT A4486 AT cygnus DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> 
> I'm not sure who the "everyone" you're referring to but I've only seen
> only one thing that could be characterised as criticism.  I thanked
> someone for understanding the reason for the change to Cygwin.
> Hopefully that was not seen as a slam against the person who submitted
> the patch.
> 
> I am also thankful that someone took the time to track down what needed
> to be changed but I haven't reached a point where I think there is a
> crying need to change cygwin back to its old behavior.  I try to
> minimize the number of options available for the CYGWIN environment
> variable, too.  This is just in the interests of not presenting too many
> things for people to tweak that make problem debugging harder.

I understand. There are already too many CYGWIN options for me to keep
track of. 

> 
> >FWIW, I *did* track down this error. It's actually in libiberty, not
> >perl, and is the result cygwin's unusual status as a unix platform
> >running under windows: _WIN32 is defined, so libiberty uses '\' as the
> >path separator. Once I figure out to whom the patch should go (since
> >everybody seems to maintain their own version -- gcc, cygwin, binutils,
> >etc) I'll submit it.
> 
> gcc and binutils have somewhat separate versions of libiberty.  Cygwin
> uses the binutils version.  The binutils version is imported from gcc
> regularly.
> 
> But you don't need to do anything.  It's already fixed in CVS in both
> binutils and gcc (and has been for some time) and I've made an
> experimental version of binutils available with the fix.

Well, that serves me right for debugging with the tarball versions
instead of CVS. :-)

--Chuck

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