Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: autoconf issues [often when upgrading from 2.13->2.53a]
Date: Mon, 22 Jul 2002 19:06:41 -0400
Message-ID: <BADF3C947A1BD54FBA75C70C241B0B9E10AA67@ex02.idirect.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Harig, Mark A." <maharig AT idirect DOT net>
To: "Nicholas Wourms" <nwourms AT yahoo DOT com>, <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g6MN6wr18863

I'm using Win2K.  

I'm pretty reluctant to point the finger at 'sed', but unfortunately I
don't have any more clues at this time.  Can you add 'set -xv' to the
generated configure script at the place in the code where 'sed' is
called, and post the result?  That, along with the input stream, could
help to debug that problem.  Also, it would help to know what
configure.in statements are generating the corresponding code in the
generated configure script, if you're able to identify those statements.

As usual, three basics are needed before the problem can be debugged:

  1. The command(s) that are "causing" the problem.
  2. The results you expected.
  3. The results you got.

> -----Original Message-----
> From: Nicholas Wourms [mailto:nwourms AT yahoo DOT com]
> Sent: Monday, July 22, 2002 6:55 PM
> To: cygwin AT cygwin DOT com
> Subject: RE: autoconf issues [often when upgrading from 2.13->2.53a]
> 
> 
> 
> --- "Harig, Mark A." <maharig AT idirect DOT net> wrote:
> > Have you tried downgrading to the stable tools (2.13) to see if the
> > problem is still occurring, or is that not an option (i.e, the
> > configure.in requires 2.53)?
> > I had a problem recently where it appeared that sed was running in
> > an
> > infinite loop.  When I downgraded to the stable tools, the problem
> > disappeared.
> 
> Unfortunately I have to use 2.53, otherwise libtool will not build
> the dll's properly.  You hit the nail right on the head, there is
> something awefully wierd going on, and I think sed is at the center
> of it.  Why just the other day I was trying to use texi2pdf, and
> wouldn't you know it sed was stuck in an infinite loop.  What OS are
> you running?  My initial opinion is that the sed is experiencing
> bit-rot.  It hasn't been updated since 2000 (the code itself since
> '98), you know.  The problem is that this is so random, there's no
> easy way to tell for sure.  I just have a hunch at this point...
> 
> Cheers,
> Nicholas
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Health - Feel better, live better
> http://health.yahoo.com
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/