I know it should be as simple as './configure [some options]' followed by 'make install', but I am at a loss knowing which options I should apply in order to have the same capabilities as another build's. For example in order to have
+BUFFY_SIZE -DEBUG -DL_STANDALONE -DOMAIN +ENABLE_NLS -EXACT_ADDRESS +HAVE_BKGDSET +HAVE_COLOR +HAVE_CURS_SET -HAVE_GETADDRINFO +HAVE_GETSID +HAVE_ICONV +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_META +HAVE_PGP +HAVE_REGCOMP +HAVE_RESIZETERM +HAVE_START_COLOR +HAVE_TYPEAHEAD -HAVE_WC_FUNCS -HOMESPOOL -ICONV_NONTRANS -ISPELL +LOCALES_HACK -SUN_ATTACHMENT -USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_GNU_REGEX -USE_GSS +USE_IMAP +USE_POP -USE_SASL -USE_SETGID +USE_SSL are all the capabilities included using "--enable-WHATEVER"? if so, why do some final results start with USE, some with HAVE, and others nothing special at all? If not, how do I enable/disable them? Additionally, is it possible to not build/install the documentation somehow? Trying to do that here gives me an error and then make stops *sigh* make[2]: Entering directory `/usr/src/mutt/doc' ##test -f manual.html || make manual.html || cp ./manual*.html ./ cp ./manual*.html ./ cp: cannot stat `./manual*.html': No such file or directory make[2]: *** [try-html] Error 1 make[2]: Leaving directory `/usr/src/mutt/doc' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/usr/src/mutt' make: *** [install] Error 2 Why would anyone want to copy ./<some file> to the same place anyway? Any why on earth would they expect that to succeed?
