On Mon, Feb 22, 2010 at 10:19:56AM +0100, Gary wrote: > 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?
The USE_* options are typically controlled via --enable-* or --with-* options to configure. The HAVE_* are system aspects that the configure script automatically detects are are not typically user configurable. The items without a prefix are primarily items which the user *may* need to override (most of these are old, but would probably be better labeled with a USE_ prefix). > 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* I am not sure, but you may be able to remove the "doc" item from the SUBDIRS variable in the Makefile. Typically it's better to just install the docbook packages so you can build the docs. See doc/devel-notes.txt for the complete list of packages required. > 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? The build system does not assume that you are building in the same directory where the sources reside. For example, if you are building mutt for multiple architectures or even different options for testing, you might create several build directories. The make target for the documentation copies from the source directory to the build directory. In the example you noted above, they are the same directory so it looks odd, but it is not in error. me
