m4_comment([$Id: conf.so,v 10.66 2007/04/05 20:36:38 bostic Exp $])m4_ref_title(Building m4_db for UNIX/POSIX systems,    Configuring m4_db,    [@configuring m4_db for UNIX systems, configuring m4_db for @UNIX systems],    build_unix/intro, build_unix/small)m4_p([dnlThere are several arguments you can specify when configuring m4_db.Although only the m4_db-specific ones are described here, most of thestandard GNU autoconf arguments are available and supported.  To see acomplete list of possible arguments, specify the --help flag to theconfigure program.])m4_p([dnlThe m4_db specific arguments are as follows:])m4_tagbeginm4_idefz(configuring without large @file support)m4_tag([m4_idef(--disable-largefile)], [dnlSome systems, notably versions of HP/UX and Solaris, require specialcompile-time options in order to create files larger than 2^32 bytes.These options are automatically enabled when m4_db is compiled.  Forthis reason, binaries built on current versions of these systems maynot run on earlier versions of the system because the library and systemcalls necessary for large files are not available.  To disable buildingwith these compile-time options, enter --disable-largefile as an argumentto configure.])m4_idefz(disabling @shared libraries, disabling @static libraries)m4_tag([m4_idef(--disable-shared), m4_idef(--disable-static)], [dnlOn systems supporting shared libraries, m4_db builds both static andshared libraries by default.  (Shared libraries are built usingm4_linkweb(http://www.gnu.org/software/libtool/libtool.html, [the GNUProject's Libtool]) distribution, which supports shared library buildson many (although not all) systems.)  To not build shared libraries,configure using the --disable-shared argument.  To not build staticlibraries, configure using the --disable-static argument.])m4_idefz(configuring m4_db @1.85 API compatibility)m4_tag([m4_idef(--enable-compat185)], [dnlTo compile or load m4_db 1.85 applications against this release of them4_db library, enter --enable-compat185 as an argument to configure.This will include m4_db 1.85 API compatibility code in the library.])m4_idefz(configuring the @C++ API)m4_tag([m4_idef(--enable-cxx)], [dnlTo build the m4_db C++ API, enter --enable-cxx as an argument toconfigure.])m4_tag([m4_idef(--enable-debug)], [dnlTo build m4_db with m4_bold(-g) as a compiler flag and withm4_bold(DEBUG) #defined during compilation, enter --enable-debug as anargument to configure.  This will create a m4_db library and utilitieswith debugging symbols, as well as load various routines that can becalled from a debugger to display pages, cursor queues, and so forth.If installed, the utilities will not be stripped.  This argument shouldnot be specified when configuring to build production binaries.])m4_tag([m4_idef(--enable-debug_rop)], [dnlTo build m4_db to output log records for read operations, enter--enable-debug_rop as an argument to configure.  This argument should notbe specified when configuring to build production binaries.])m4_tag([m4_idef(--enable-debug_wop)], [dnlTo build m4_db to output log records for write operations, enter--enable-debug_wop as an argument to configure.  This argument should notbe specified when configuring to build production binaries.])m4_tag([m4_idef(--enable-diagnostic)], [dnlTo build m4_db with run-time debugging checks, enter --enable-diagnosticas an argument to configure.  This causes a number of additional checksto be performed when m4_db is running, and also causes some failures totrigger process abort rather than returning errors to the application.Applications built using this argument should not share databaseenvironments with applications built without this argument.  Thisargument should not be specified when configuring to build productionbinaries.])m4_idefz(building a utility to dump m4_db @1.85 databases)m4_tag([m4_idef(--enable-dump185)], [dnlTo convert m4_db 1.85 (or earlier) databases to this release of m4_db,enter --enable-dump185 as an argument to configure.  This will build them4_ref(db_dump185) utility, which can dump m4_db 1.85 and 1.86 databasesin a format readable by the m4_db m4_ref(db_load) utility.m4_p([dnlThe system libraries with which you are loading the m4_ref(db_dump185)utility must already contain the m4_db 1.85 library routines for thisto work because the m4_db distribution does not include them.  If youare using a non-standard library for the m4_db 1.85 library routines,you will have to change the Makefile that the configuration step createsto load the m4_ref(db_dump185) utility with that library.])])m4_idefz(configuring the @Java API)m4_tag([m4_idef(--enable-java)], [dnlTo build the m4_db Java API, enter --enable-java as an argument toconfigure. To build Java, you must also build with shared libraries.Before configuring, you must set your PATH environment variable toinclude javac.  Note that it is not sufficient to include a symboliclink to javac in your PATH because the configuration process uses thelocation of javac to determine the location of the Java include files(for example, jni.h). On some systems, additional include directoriesmay be needed to process jni.h; see m4_link(flags, Changing compile orload options) for more information.])m4_idefz(configuring the fine-grained lock manager)m4_tag([m4_idef(--enable-fine_grained_lock_manager)], [dnlFor highly concurrent m4_db applications on multithreaded, multi-corearchitectures (for example, Sun Microsystem's Niagara systems), it maybe advantageous to configure m4_db for finer-grained locking behaviorin the lock manager subsystem.  To build with m4_db with finer-grainedlocking behavior in the lock manager subsystem, enter--enable-fine_grained_lock_manager as an argument to configure.  Thisoption should not be configured without performance testing to confirmthe finer-grained locking behavior increases overall throughput, as thisoption will decrease overall throughput for some applications.])m4_tag([m4_idef(--enable-posixmutexes)], [dnlTo force m4_db to use the POSIX pthread mutex interfaces for underlyingmutex support, enter --enable-posixmutexes as an argument to configure.This is rarely necessary: POSIX mutexes will be selected automaticallyon systems where they are the preferred implementation.m4_p([dnlThe --enable-posixmutexes configuration argument is normally used intwo ways: First, when there are multiple mutex implementations availableand the POSIX mutex implementation is not the preferred one (forexample, on Solaris where the LWP mutexes are used by default).  Second,by default the m4_db library will only select the POSIX muteximplementation if it supports mutexes shared between multiple processes,as described for the pthread_condattr_setpshared andpthread_mutexattr_setpshared interfaces.  The --enable-posixmutexesconfiguration argument can be used to force the selection of POSIXmutexes in this case, which can improve application performancesignificantly when the alternative mutex implementation is anon-blocking one (for example test-and-set assembly instructions).However, configuring to use POSIX mutexes when the implementation doesnot have inter-process support will only allow the creation of privatedatabase environments, that is, environments where them4_ref(DB_PRIVATE) flag is specified to the m4_refT(dbenv_open).])m4_p([dnlSpecifying the --enable-posixmutexes configuration argument may requirethat applications and m4_db be linked with the -lpthread library.])])m4_tag([m4_idef(--enable-pthread_api)], [dnlTo configure m4_db for a POSIX pthreads application (with the exceptionthat POSIX pthread mutexes may not be selected as the underlying muteximplementation for the build), enter --enable-pthread_api as an argumentto configure.  The build will include the m4_db replication managerinterfaces and will use the POSIX standard pthread_self andpthread_yield functions to identify threads of control and yield theprocessor.  The --enable-pthread_api argument requires POSIX pthreadsupport already be installed on your system.m4_p([dnlSpecifying the --enable-pthread_api configuration argument may requirethat applications and m4_db be linked with the -lpthread library.])])m4_idefz(configuring a @RPC client/server)m4_tag([m4_idef(--enable-rpc)], [dnlTo build the m4_db RPC client code and server utility, enter --enable-rpcas an argument to configure.  The --enable-rpc argument requires that RPCsupport already be installed on your system.])m4_idefz(configuring a small memory @footprint library)m4_tag([m4_idef(--enable-smallbuild)], [dnlTo build a small memory footprint version of the m4_db library, enter--enable-smallbuild as an argument to configure.  The--enable-smallbuild argument is equivalent to individually specifying--disable-cryptography, --disable-hash, --disable-queue,--disable-replication, --disable-statistics and --disable-verify,turning off cryptography support, the Hash and Queue access methods,database environment replication support and database verificationsupport.  See m4_linkpage(M4RELDIR/ref/build_unix/small, Building asmall memory footprint library) for more information.])m4_idefz(configuring the @Tcl API)m4_tag([m4_idef(--enable-tcl)], [dnlTo build the m4_db Tcl API, enter --enable-tcl as an argument toconfigure.  This configuration argument expects to find Tcl's tclConfig.shfile in the m4_path(/usr/local/lib) directory.  See the --with-tclargument for instructions on specifying a non-standard location for theTcl installation.  See m4_link(M4RELDIR/ref/tcl/intro, Loading m4_dbwith Tcl) for information on sites from which you can download Tcl andwhich Tcl versions are compatible with m4_db.  To build Tcl, you mustalso build with shared libraries.])m4_idefz(configuring the @test suite)m4_tag([m4_idef(--enable-test)], [dnlTo build the m4_db test suite, enter --enable-test as an argument toconfigure.  To run the m4_db test suite, you must also build the TclAPI.  This argument should not be specified when configuring to buildproduction binaries.])m4_tag([m4_idef(--enable-uimutexes)], [dnlTo force m4_db to use the UNIX International (UI) mutex interfaces forunderlying mutex support, enter --enable-uimutexes as an argument toconfigure.  This is rarely necessary: UI mutexes will be selectedautomatically on systems where they are the preferred implementation.m4_p([dnlThe --enable-uimutexes configuration argument is normally used whenthere are multiple mutex implementations available and the UI muteximplementation is not the preferred one (for example, on Solaris wherethe LWP mutexes are used by default).])m4_p([dnlSpecifying the --enable-uimutexes configuration argument may requirethat applications and m4_db be linked with the -lthread library.])])m4_tag([m4_idef(--enable-umrw)], [dnlRational Software's Purify product and other run-time tools complainabout uninitialized reads/writes of structure fields whose only purposeis padding, as well as when heap memory that was never initialized iswritten to disk.  Specify the --enable-umrw argument duringconfiguration to mask these errors.  This argument should not bespecified when configuring to build production binaries.])m4_tag([m4_idef(--with-mutex=MUTEX)], [dnlTo force m4_db to use a specific mutex implementation, configure with--with-mutex=MUTEX, where MUTEX is the mutex implementation you want.For example, --with-mutex=x86/gcc-assembly will configure m4_db to usethe x86 GNU gcc compiler based test-and-set assembly mutexes.  This israrely necessary and should be done only when the default configurationselects the wrong mutex implementation.  A list of available muteximplementations can be found in the distribution filem4_path(dist/aclocal/mutex.ac).])m4_tag([m4_idef(--with-tcl=DIR)], [dnlTo build the m4_db Tcl API, enter --with-tcl=DIR, replacing DIR withthe directory in which the Tcl tclConfig.sh file may be found.  Seem4_link(M4RELDIR/ref/tcl/intro, Loading m4_db with Tcl) for informationon sites from which you can download Tcl and which Tcl versions arecompatible with m4_db.  To build Tcl, you must also build with sharedlibraries.])m4_tag([m4_idef(--with-uniquename=NAME)], [dnlTo build m4_db with unique symbol names (in order to avoid conflictswith other application modules or libraries), enter --with-uniquename=NAME,replacing NAME with a string that to be appended to every m4_db symbol.If "=NAME" is not specified, a default value of "_MAJORMINOR" is used,where MAJORMINOR is the major and minor release numbers of the m4_dbrelease.  See m4_link(M4RELDIR/ref/install/multiple, Building withmultiple versions of m4_db) for more information.])m4_tagendm4_page_footer