Re: configure question.



> Soemtimes when I am compiling an app, I'll run configure, and it will go
> through its thing and everything will be fine.  then when I run make, it
> goes and runs autoconf, automake, etc and then re-runs configure.  My
> question is why does it do this?  Why not just begin compiling?

    This usually happens when you've changed configure.in and make has
detected it's changed and runs autoconf and then configure. I've only seen
it happen after I've run ./configure for the first time when I've updated
something from CVS and it's changed configure.in, and I've forgotten to run
autoconf  to update the configure script.

Iain



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]