This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: configure-script failure


Igor Pechtchanski wrote:

On Mon, 30 Aug 2004, Jani tiainen wrote:

Christopher Faylor 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?"


Help, it appeared again... =)

Well here is more info:

No config.log appears to be generated (or there is previous log, not even
erased), error produced is:

$ ./configure --disable-gtk-doc --prefix=/target --disable-static
configure: error: invalid feature name: static

Error seems to change according to last parameter, but not always. Sometimes I
get error regarding "gtk-doc".


It does appear often, but "randomly". I haven't noticed difference
between several configure scripts run. Observation shows that it might
something to do that configure script is fetched from HD instead of
memory cache..


"configure -v"?  "bash -x configure"?  Come on, man, do some *debugging*!
    Igor

Hard to do since it's not reproducible, it just comes and goes. And second thing, I'm just an user that reports a problem. Problem itself can't be configure since it appears on several unrelated configure scripts, randomly. Same script might run or not and it always works on second time.


Debugging this is not worth of my time. I have even used more time to write this message than inconvenience about sometimes erroenous first run gives to me.

--

Jani Tiainen



--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]