Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Content-class: urn:content-classes:message
Subject: RE: configure-script failure
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 30 Aug 2004 17:44:07 +0200
Message-ID: <90459864DAD67D43BDD3D517DEFC2F7D70BE@axon.Axentia.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Peter Ekberg" <peda AT axentia DOT se>
To: <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i7UFgPCY027599

Christopher wrote:
> On Mon, Aug 30, 2004 at 10:21:46AM -0400, Igor Pechtchanski wrote:
> >On Mon, 30 Aug 2004, bertrand marquis wrote:
> >>Le lun 30/08/2004 ?  07:50, Jani tiainen a ?crit :
> >>>Why sometimes running ./configure doesn't work?
> >>>
> >>>Usually it reports that some feature is missing, but running second
> >>>time with same parameters doesn't produce error..
> >>>
> >>>like:
> >>>
> >>>configure --prefix=/target --disable-static
> >>>
> >>>in first run I usually get "no such feature 'static'" (or 
> similiar).
> >>>On second run with exactly same parameters it works.
> >>>
> >>>Any explanations for a such behavior?
> >>
> >>Hello i run through the same problem from times to times running
> >>configure scripts and i didn't find any other solution than 
> running the
> >>configure again.  This is quite borring and i was not able 
> to find any
> >>solution.
> >>
> >>I would also be interested in a solution or an explanation 
> if someone
> >>has one.
> >
> >The usual advice for any configure problem is to look at the 
> config.log
> >file from the failed run of configure (beware, the file is 
> overwritten
> >every time configure is run).  FWIW, you and Jani may have different
> >problems altogether.
> 
> However, regardless of whether they are similar or not, we'd actually
> need *details* for figuring out problems like this, i.e.,
> 
> http://cygwin.com/problems.html
> 
> Otherwise, these messages boil down to:
> 
> "I noticed that sometimes my car won't start but then I wait a little
> while and it does!"
> 
> "I have the same problem!  Can someone help?"

I believe this is yet another instance of the problem that I have
described here:
http://sources.redhat.com/ml/cygwin/2004-08/msg01025.html

Seems like more than a few people are hitting this sore spot.

Further investigation of my original case indeed shows that consecutive
runs of configure need not result in the same output. The spaces I
threw into the mix are probably of no consequence.

When I try to slim down the configure script to produce a more
manageable test case, the bug apparently gets harder to trigger the
more I trim from the configure script.

Looks like a race to me.

Cheers,
Peter

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/