Kyle Jones <kyle_jones(a)wonderworks.com> writes in xemacs-beta(a)xemacs.org:
...
configure spews a long series of messages. A warning will be
lost in all that.
I agree. I've always thought the defaulting of configure output to
verbose makes the problem worse if anything.
I build XEmacs like this
./configure; make
Fascinating. Configure has so many bogus defaults for my system I
can't do that and get an XEmacs I wish to run.
and then go do something else while it grinds. If we expect people
to pay attention to the warnings, either configure has to generate much
less output or configure has to abort, so that the user is forced
to read the message and take some action.
We probably need a quiet option that only prints out fatal error
messages. It really depends on the speed of the machine you're
building XEmacs on. I've been really annoyed at spending 20 minutes
configuring XEmacs on a slow Sparc only to find it chose the wrong
options and on a fast machine it doesn't matter.