At 9/26/2005 10:17 PM, Himanshu Gohel wrote:
> > Interesting. How/where can I read more about what all these
> > packages/things (nls, mod-activation, be, axps, shared) do
> > and/or how they are used?
>Part of the answer there was in what you snipped:
Part of it, but a very small part as per the excerpt below. It lists just
a couple packages, ones that I know a little about already; however I don't
know what those things do, nor what happens when they are disabled. Also,
some packages are not even listed (eg, the "nls" package) and for those I
have even less info.
I'm curious if there's a doc set somewhere that describes all these
packages? I have yet to see anything in any docs (although I have yet to
do a thorough search--I was hoping someone here would point me in the right
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-apr=PATH prefix for installed APR, path to APR build tree,
or the full path to apr-config
--with-apr-util=PATH prefix for installed APU, path to APU build tree,
or the full path to apu-config
--with-gnu-ld assume the C compiler uses GNU ld [default=no]
--with-pic try to use only PIC/non-PIC objects [default=use
include additional configurations [automatic]
--with-neon=PREFIX Determine neon library configuration based on
'PREFIX/bin/neon-config'. Default is to search for
neon in a subdirectory of the top source directory
and then to look for neon-config in $PATH.
--with-apache=DIR Build static Apache module. DIR is the path to the
top-level Apache source directory.
--with-apxs[=FILE] Build shared Apache module. FILE is the optional
pathname to the Apache apxs tool; defaults to
The Subversion Berkeley DB based filesystem library
requires Berkeley DB $db_version or newer. If you
specify `--without-berkeley-db', that library will
not be built. Otherwise, the configure script
that library if and only if APR-UTIL is linked
against a new enough version of Berkeley DB.
If and only if you are building APR-UTIL as part of
the Subversion build process, you may help APR-UTIL
to find the correct Berkeley DB installation by
passing a PATH to this option, to cause APR-UTIL to
look for the Berkeley DB header and library in
`PATH/include' and `PATH/lib'. If PATH is of the
form `HEADER:LIB', then search for header files in
HEADER, and the library in LIB. If you omit the
`=PATH' part completely, the configure script will
search for Berkeley DB in a number of standard
--with-ssl This option does NOT affect the Subversion build
process in any way. It enables OpenSSL support in
the Neon library. If and only if you are building
Neon as an integrated part of the Subversion build
process, rather than linking to an already installed
version of Neon, you probably want to pass this
option so that Neon (and so indirectly, Subversion)
will be capable of https:// access.
--with-editor=PATH Specify a default editor for the subversion client.
--with-zlib enable zlib support
--with-jdk=PATH Try to use 'PATH/include' to find the JNI headers.
If PATH is not specified, look for a Java
Development Kit at JAVA_HOME.
--with-jikes=PATH Specify the path to a jikes binary to use it as your
Java compiler. The default is to look for jikes
(PATH optional). This behavior can be switched off
by supplying 'no'.
--with-swig=PATH Try to use 'PATH/bin/swig' to build the swig
bindings. If PATH is not specified, look for a
'swig' binary in your PATH.
install Ruby bindings in SITEDIR (default is same as
--with-junit=PATH Specify a path to the junit JAR file.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Sep 27 12:07:39 2005