configure requires everything?!?

Stu Tomlinson stu at
Fri Aug 22 10:32:55 EDT 2008

On Fri, 2008-08-22 at 10:25 -0400, hymie! wrote:

> Why can't ./configure just assume that if I'm missing some of these things,
> I don't want them  (like it used to)?

Because requiring users explicitly override dependencies ensures that we
are dealing with a known set of functionality in the majority of cases -
and in other cases the user will know they did something "different".

If you know you have all the dependencies you need, and don't want to
manually disable them individually, the old behavior can be replicated
   ./configure --disable-missing-dependencies



More information about the Support mailing list