"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "man/dacs.install.7.xml" between
dacs-1.4.45.txz and dacs-1.4.46.txz

About: DACS (Distributed Access Control System) is a light-weight single sign-on and role-based access control system for web servers and server-based software.

dacs.install.7.xml  (dacs-1.4.45.txz):dacs.install.7.xml  (dacs-1.4.46.txz)
skipping to change at line 13 skipping to change at line 13
<!ENTITY version SYSTEM "version.xml"> <!ENTITY version SYSTEM "version.xml">
<!ENTITY insert-author SYSTEM "author-stmt.xml"> <!ENTITY insert-author SYSTEM "author-stmt.xml">
<!ENTITY insert-copyright SYSTEM "copyright-stmt.xml"> <!ENTITY insert-copyright SYSTEM "copyright-stmt.xml">
]> ]>
<!-- <!--
Copyright (c) 2003-2021 Copyright (c) 2003-2021
Distributed Systems Software. All rights reserved. Distributed Systems Software. All rights reserved.
See the file LICENSE for redistribution information. See the file LICENSE for redistribution information.
$Id: dacs.install.7.xml 3168 2021-01-19 23:57:10Z brachman $ $Id: dacs.install.7.xml 3181 2021-06-08 20:03:18Z brachman $
--> -->
<!-- The output filename is generated from refentry content elements. <!-- The output filename is generated from refentry content elements.
The filename prefix is the refname and the suffix is the The filename prefix is the refname and the suffix is the
manvolnum from within the refmeta element. manvolnum from within the refmeta element.
--> -->
<refentry id="dacs.install"> <refentry id="dacs.install">
<refmeta> <refmeta>
<refentrytitle>dacs.install</refentrytitle> <refentrytitle>dacs.install</refentrytitle>
skipping to change at line 662 skipping to change at line 662
<systemitem class="library">Readline</systemitem>: Command line history and edit ing</link> <systemitem class="library">Readline</systemitem>: Command line history and edit ing</link>
</para></listitem> </para></listitem>
</itemizedlist> </itemizedlist>
</highlights> </highlights>
<orderedlist> <orderedlist>
<listitem id="install-expat"><para>Install the <application>Expat</application> XML parser <listitem id="install-expat"><para>Install the <application>Expat</application> XML parser
</para> </para>
<para>This release of <command>DACS</command> has been tested with <para>This release of <command>DACS</command> has been tested with
<ulink url="https://libexpat.github.io/">Expat</ulink> <ulink url="https://github.com/libexpat/libexpat/releases">Expat</ulink>
<literal class="version">2.2.10</literal> and we recommend that <literal class="version">2.4.1</literal> and we recommend that
you use that release. you use that release.
</para> </para>
<para>For use with <command>DACS</command>, <para>For use with <command>DACS</command>,
<command>Expat</command> can either be built with <command>Expat</command> can either be built with
<option>-prefix=/usr/local</option> or something like <option>-prefix=/usr/local</option> or something like
<option>-prefix=/usr/local/expat-2.2.10</option>, <option>-prefix=/usr/local/expat-2.4.1</option>,
whichever you prefer. whichever you prefer.
In the former case, you can omit the In the former case, you can omit the
<option>--with-expat</option> when configuring <option>--with-expat</option> when configuring
<command>DACS</command> or use <option>--with-expat=/usr/local</option>, <command>DACS</command> or use <option>--with-expat=/usr/local</option>,
and in the latter case you must use and in the latter case you must use
<option>--with-expat=/usr/local/expat-2.2.10</option>. <option>--with-expat=/usr/local/expat-2.4.1</option>.
After <command>Expat</command> has been unpacked, After <command>Expat</command> has been unpacked,
we currently build <command>Expat</command> using the more recent we currently build <command>Expat</command> using the more recent
<command>cmake</command> method: <command>cmake</command> method:
<programlisting> <programlisting>
% cd expat-2.2.10 % cd expat-2.4.1
% mkdir build &amp;&amp; cd build % mkdir build &amp;&amp; cd build
% cmake -DCMAKE_INSTALL_PREFIX=/usr/local/expat-2.2.10 ../expat % cmake -DCMAKE_INSTALL_PREFIX=/usr/local/expat-2.4.1 ../
% make % make
(All should go well.) (All should go well.)
% make test % make test
(All should go well.) (All should go well.)
% make install % make install
(All should go well here, too.) (All should go well here, too.)
</programlisting> </programlisting>
Alternatively, if <command>cmake</command> is unavailable, Alternatively, if <command>cmake</command> is unavailable,
from the <command>Expat</command> distribution's source directory from the <command>Expat</command> distribution's source directory
(possibly called <filename class="directory">expat</filename>) (possibly called <filename class="directory">expat</filename>)
and, if necessary, after creating the <command>configure</command> script and, if necessary, after creating the <command>configure</command> script
by running <filename>./buildconf.sh</filename>): by running <filename>./buildconf.sh</filename>):
<programlisting> <programlisting>
% cd expat-2.2.10 % cd expat-2.4.1
% ./configure --prefix=/usr/local/expat-2.2.10 % ./configure --prefix=/usr/local/expat-2.4.1
% make % make
(All should go well.) (All should go well.)
% make install % make install
(All should go well here, too.) (All should go well here, too.)
</programlisting> </programlisting>
</para> </para>
<note id="note2" xreflabel="Win2K/Cygwin notes"><para>On <note id="note2" xreflabel="Win2K/Cygwin notes"><para>On
<systemitem class="osname">Win2K/Cygwin</systemitem>, <systemitem class="osname">Win2K/Cygwin</systemitem>,
only a static library is needed. only a static library is needed.
skipping to change at line 724 skipping to change at line 724
<option>--enable-static=yes</option> and try to build it again. <option>--enable-static=yes</option> and try to build it again.
</para></note> </para></note>
</listitem> </listitem>
<listitem id="install-openssl"><para>Install <command>OpenSSL</command> <listitem id="install-openssl"><para>Install <command>OpenSSL</command>
</para> </para>
<para><command>DACS</command> requires cryptographic functionality <para><command>DACS</command> requires cryptographic functionality
provided by <ulink url="https://www.openssl.org">OpenSSL</ulink>. provided by <ulink url="https://www.openssl.org">OpenSSL</ulink>.
This release of <command>DACS</command> has been tested with This release of <command>DACS</command> has been tested with
<literal class="version">openssl-1.1.1i</literal> <literal class="version">openssl-1.1.1k</literal>
and we recommend that you use that release with <command>DACS</command>. and we recommend that you use that release with <command>DACS</command>.
<command>Apache</command> should be built using the version of <command>Apache</command> should be built using the version of
<command>OpenSSL</command> recommended by the particular <command>OpenSSL</command> recommended by the particular
<command>Apache</command> release - using a more recent version <command>Apache</command> release - using a more recent version
of <command>OpenSSL</command> may introduce build problems or run-time bugs of <command>OpenSSL</command> may introduce build problems or run-time bugs
in <command>Apache</command>. in <command>Apache</command>.
<emphasis>It is not necessary for <command>Apache</command> and <emphasis>It is not necessary for <command>Apache</command> and
<command>DACS</command> to use the same release of <command>DACS</command> to use the same release of
<command>OpenSSL</command></emphasis>. <command>OpenSSL</command></emphasis>.
</para> </para>
skipping to change at line 762 skipping to change at line 762
</para></listitem> </para></listitem>
<listitem><para>In some configurations you may want or require shared <listitem><para>In some configurations you may want or require shared
<command>OpenSSL</command> libraries; if so, add the <option>shared</option> <command>OpenSSL</command> libraries; if so, add the <option>shared</option>
command line flag to <command>config</command> command line flag to <command>config</command>
when building <command>OpenSSL</command>. when building <command>OpenSSL</command>.
</para></listitem> </para></listitem>
<listitem><para>Here is how we built <command>OpenSSL</command>: <listitem><para>Here is how we built <command>OpenSSL</command>:
<programlisting class="small_listing"> <programlisting class="small_listing">
% ./config --prefix=/usr/local/openssl-1.1.1i --openssldir=/usr/local/openssl-1. % ./config --prefix=/usr/local/openssl-1.1.1k --openssldir=/usr/local/openssl-1.
1.1i \ 1.1k \
-fPIC shared "-Wl,-rpath,/usr/local/openssl-1.1.1i/lib" -fPIC shared "-Wl,-rpath,/usr/local/openssl-1.1.1k/lib"
</programlisting> </programlisting>
</para></listitem> </para></listitem>
<listitem><para>On <systemitem class="osname">macOS</systemitem>, <listitem><para>On <systemitem class="osname">macOS</systemitem>,
however, it was necessary to explicitly request however, it was necessary to explicitly request
a 64-bit build of <command>OpenSSL</command>: a 64-bit build of <command>OpenSSL</command>:
<programlisting class="small_listing"> <programlisting class="small_listing">
% ./Configure darwin64-x86_64-cc --prefix=/usr/local/openssl-1.1.1i \ % ./Configure darwin64-x86_64-cc --prefix=/usr/local/openssl-1.1.1k \
--openssldir=/usr/local/openssl-1.1.1i -fPIC shared --openssldir=/usr/local/openssl-1.1.1k -fPIC shared
</programlisting> </programlisting>
</para></listitem> </para></listitem>
</itemizedlist> </itemizedlist>
</para></note> </para></note>
</listitem> </listitem>
<listitem id="install-apache"><para>Install <application>Apache</application> <listitem id="install-apache"><para>Install <application>Apache</application>
<literal class="version">2.4.46</literal> <literal class="version">2.4.48</literal>
</para> </para>
<para>You will need an SSL/TLS-capable <para>You will need an SSL/TLS-capable
<ulink url="https://httpd.apache.org">Apache</ulink> server <ulink url="https://httpd.apache.org">Apache</ulink> server
(build <command>Apache</command> with <option>--enable-ssl</option>) that uses (build <command>Apache</command> with <option>--enable-ssl</option>) that uses
a recent version of <command>OpenSSL</command> a recent version of <command>OpenSSL</command>
(build <command>Apache</command> using (build <command>Apache</command> using
<option>--with-ssl=<replaceable>path</replaceable></option>, <option>--with-ssl=<replaceable>path</replaceable></option>,
see <ulink url="#install-openssl">above</ulink>). see <ulink url="#install-openssl">above</ulink>).
</para> </para>
skipping to change at line 847 skipping to change at line 847
make sure that <function>mod_so</function> is built-in to make sure that <function>mod_so</function> is built-in to
your <command>httpd</command> your <command>httpd</command>
("<literal>httpd -l</literal>" displays a list). ("<literal>httpd -l</literal>" displays a list).
</para> </para>
<important id="important4" xreflabel="Installing Apache"><para> <important id="important4" xreflabel="Installing Apache"><para>
<itemizedlist> <itemizedlist>
<listitem><para>This release of <command>DACS</command> has been <listitem><para>This release of <command>DACS</command> has been
tested with tested with
<command>Apache</command> <literal class="version">2.4.46</literal>. <command>Apache</command> <literal class="version">2.4.48</literal>.
</para></listitem> </para></listitem>
<listitem><para>Detailed instructions for building <listitem><para>Detailed instructions for building
<command>Apache</command> <literal class="version">2.4.46</literal> <command>Apache</command> <literal class="version">2.4.48</literal>
can be found in Apache's can be found in Apache's
<filename>INSTALL</filename> file. <filename>INSTALL</filename> file.
For the testing platforms, we get the For the testing platforms, we get the
<systemitem class="library">APR</systemitem> and <systemitem class="library">APR</systemitem> and
<systemitem class="library">APR-UTIL</systemitem> <systemitem class="library">APR-UTIL</systemitem>
libraries from libraries from
<ulink url="https://apr.apache.org">apr.apache.org</ulink> and unpack <ulink url="https://apr.apache.org">apr.apache.org</ulink> and unpack
them in the Apache distribution's them in the Apache distribution's
<filename class="directory">srclib</filename> directory, then rename them <filename class="directory">srclib</filename> directory, then rename them
<filename class="directory">srclib/apr</filename> and <filename class="directory">srclib/apr</filename> and
<filename class="directory">srclib/apr-util</filename>, respectively, <filename class="directory">srclib/apr-util</filename>, respectively,
as it says in <filename>INSTALL</filename>. as it says in <filename>INSTALL</filename>.
We currently use We currently use
<systemitem class="library">apr-1.7.0</systemitem> and <systemitem class="library">apr-1.7.0</systemitem> and
<systemitem class="library">apr-util-1.6.1</systemitem>. <systemitem class="library">apr-util-1.6.1</systemitem>.
If you are building <command>httpd</command> this way, If you are building <command>httpd</command> this way,
include the <option>--with-included-apr</option> flag include the <option>--with-included-apr</option> flag
with <command>configure</command>, such as: with <command>configure</command>, such as:
<screen> <screen>
# ./configure --prefix=/usr/local/apache2-2.4.46 --enable-ssl=static \ # ./configure --prefix=/usr/local/apache2-2.4.48 --enable-ssl=static \
--with-ssl=/usr/local/openssl-1.1.1i --with-included-apr --with-ssl=/usr/local/openssl-1.1.1k --with-included-apr \
LDFLAGS="-L/usr/local/openssl-1.1.1k/lib -Wl,-rpath,/usr/local/openssl-1.1.1
k/lib"
</screen> </screen>
</para></listitem> </para></listitem>
<listitem><para>On <systemitem class="osname">CentOS</systemitem> <listitem><para>On <systemitem class="osname">CentOS</systemitem>
<literal class="version">5.9</literal> and later, <literal class="version">5.9</literal> and later,
the <command>Apache</command> build may fail with a complaint the <command>Apache</command> build may fail with a complaint
about not finding <command>pcre-config</command>. about not finding <command>pcre-config</command>.
To solve this, try: To solve this, try:
<screen> <screen>
# yum install pcre-devel.x86_64 # yum install pcre-devel.x86_64
skipping to change at line 894 skipping to change at line 895
</para></listitem> </para></listitem>
<listitem><para>If suitable <listitem><para>If suitable
<systemitem class="library">APR</systemitem>, <systemitem class="library">APR</systemitem>,
<systemitem class="library">APR-UTIL</systemitem>, <systemitem class="library">APR-UTIL</systemitem>,
and other support libraries have already been installed on your system, and other support libraries have already been installed on your system,
you may be able to perform a basic build and install of you may be able to perform a basic build and install of
<command>Apache</command> <literal class="version">2.4</literal> <command>Apache</command> <literal class="version">2.4</literal>
with a command like: with a command like:
<programlisting> <programlisting>
% cd httpd-2.4.46 % cd httpd-2.4.48
% ./configure --prefix=/usr/local/apache2-2.4.46 --enable-ssl \ % ./configure --prefix=/usr/local/apache2-2.4.48 --enable-ssl \
--with-ssl=/usr/local/openssl-1.1.1i --with-ssl=/usr/local/openssl-1.1.1k
% make install % make install
</programlisting> </programlisting>
</para></listitem> </para></listitem>
<listitem><para>We sometimes run into minor problems configuring or building <listitem><para>We sometimes run into minor problems configuring or building
<command>Apache</command> <literal class="version">2.4</literal> <command>Apache</command> <literal class="version">2.4</literal>
on <systemitem class="osname">macOS</systemitem>, on <systemitem class="osname">macOS</systemitem>,
especially after a recent especially after a recent
<ulink url="https://developer.apple.com/xcode">Xcode</ulink> upgrade. <ulink url="https://developer.apple.com/xcode">Xcode</ulink> upgrade.
Ensure your <envar>PATH</envar> is correct. Ensure your <envar>PATH</envar> is correct.
skipping to change at line 973 skipping to change at line 974
<para>If you encounter problems building <command>dacsversion</command>, <para>If you encounter problems building <command>dacsversion</command>,
it may be necessary for you to go back and build it may be necessary for you to go back and build
<systemitem class="library">APR</systemitem> with the <systemitem class="library">APR</systemitem> with the
<option>--disable-lfs</option> flag to disable large file support on your <option>--disable-lfs</option> flag to disable large file support on your
platform. platform.
</para> </para>
<para>On <systemitem class="osname">FreeBSD</systemitem>, <para>On <systemitem class="osname">FreeBSD</systemitem>,
when doing the top level <command>Apache</command> configuration above when doing the top level <command>Apache</command> configuration above
it was necessary to add it was necessary to add
"<literal>-rpath /usr/local/db-5.3.28/lib -rpath /usr/local/openssl-1.1.1i/lib</ literal>" to "<literal>-rpath /usr/local/db-5.3.28/lib -rpath /usr/local/openssl-1.1.1k/lib</ literal>" to
<varname>LDFLAGS</varname> so that Apache commands could find <varname>LDFLAGS</varname> so that Apache commands could find
shared libraries at run time. shared libraries at run time.
</para> </para>
<para>On <systemitem class="osname">CentOS</systemitem>, <para>On <systemitem class="osname">CentOS</systemitem>,
when building <filename class="directory">apr-util</filename>, when building <filename class="directory">apr-util</filename>,
and at the top level, it was necessary to use and at the top level, it was necessary to use
(instead of the <literal>-rpath</literal> flags) (instead of the <literal>-rpath</literal> flags)
"<literal>-Wl,-rpath /usr/local/db-5.3.28/lib -Wl,-rpath /usr/local/openssl-1.1. 1i/lib</literal>" to <varname>LDFLAGS</varname>. "<literal>-Wl,-rpath /usr/local/db-5.3.28/lib -Wl,-rpath /usr/local/openssl-1.1. 1k/lib</literal>" to <varname>LDFLAGS</varname>.
</para> </para>
<para>Alternatively, on either platform the <command>ldconfig</command> command <para>Alternatively, on either platform the <command>ldconfig</command> command
or <envar>LD_LIBRARY_PATH</envar> might be used. or <envar>LD_LIBRARY_PATH</envar> might be used.
It appears that the <varname>LDFLAGS</varname> above should be omitted It appears that the <varname>LDFLAGS</varname> above should be omitted
on <systemitem class="osname">macOS</systemitem>. on <systemitem class="osname">macOS</systemitem>.
</para></listitem> </para></listitem>
<listitem><para>In some configurations an <listitem><para>In some configurations an
"<literal>undefined ssl_hook_Fixup symbol</literal>", "<literal>undefined ssl_hook_Fixup symbol</literal>",
skipping to change at line 1010 skipping to change at line 1011
<systemitem class="library">libssl.so</systemitem> and <systemitem class="library">libssl.so</systemitem> and
<systemitem class="library">libcrypto.so</systemitem> are, <systemitem class="library">libcrypto.so</systemitem> are,
even though the correct path was specified at Apache build time through even though the correct path was specified at Apache build time through
the <option>--with-ssl</option> flag to <command>configure</command>. the <option>--with-ssl</option> flag to <command>configure</command>.
</para> </para>
<para>One solution is to make <function>mod_ssl</function> a built-in module <para>One solution is to make <function>mod_ssl</function> a built-in module
instead of a dynamically loaded module. instead of a dynamically loaded module.
Build <command>Apache</command> using something similar to this (using the Build <command>Apache</command> using something similar to this (using the
<option>--enable-ssl=static</option> flag is the important change): <option>--enable-ssl=static</option> flag is the important change):
<screen> <screen>
% ./configure --prefix=/usr/local/apache2-2.4.46 \ % ./configure --prefix=/usr/local/apache2-2.4.48 \
--with-ssl=/usr/local/openssl-1.1.1i --enable-ssl=static --with-ssl=/usr/local/openssl-1.1.1k --enable-ssl=static
</screen> </screen>
Then do a "<userinput>make install</userinput>". Then do a "<userinput>make install</userinput>".
Note that you will need to comment out the Note that you will need to comment out the
<filename>httpd.conf</filename> directive <filename>httpd.conf</filename> directive
that loads <function>mod_ssl</function>: that loads <function>mod_ssl</function>:
<screen> <screen>
# LoadModule ssl_module modules/mod_ssl.so # LoadModule ssl_module modules/mod_ssl.so
</screen> </screen>
</para> </para>
skipping to change at line 1039 skipping to change at line 1040
you will see an error message like this: you will see an error message like this:
<screen> <screen>
error while loading shared libraries: libssl.so.1.0.0: cannot open error while loading shared libraries: libssl.so.1.0.0: cannot open
shared object file: No such file or directory shared object file: No such file or directory
</screen> </screen>
Tell the linker where the <command>OpenSSL</command> libraries are by Tell the linker where the <command>OpenSSL</command> libraries are by
setting the setting the
<envar>LD_LIBRARY_PATH</envar> environment variable for <envar>LD_LIBRARY_PATH</envar> environment variable for
<command>httpd</command>; for example: <command>httpd</command>; for example:
<screen> <screen>
% sh -c "export LD_LIBRARY_PATH=/usr/local/openssl-1.1.1i/lib; bin/httpd -M" % sh -c "export LD_LIBRARY_PATH=/usr/local/openssl-1.1.1k/lib; bin/httpd -M"
</screen> </screen>
You may also be able to resolve the problem using You may also be able to resolve the problem using
the <command>ldconfig</command> command, the <command>ldconfig</command> command,
but we don't know if that could possibly break other programs that but we don't know if that could possibly break other programs that
expect a different version of the <command>OpenSSL</command> library. expect a different version of the <command>OpenSSL</command> library.
You will need to always set <envar>LD_LIBRARY_PATH</envar> before running You will need to always set <envar>LD_LIBRARY_PATH</envar> before running
<command>httpd</command>, maybe using an alias or script. <command>httpd</command>, maybe using an alias or script.
If you use <command>apachectl</command> to manage <command>Apache</command>, If you use <command>apachectl</command> to manage <command>Apache</command>,
you could simply have it set <envar>LD_LIBRARY_PATH</envar> you could simply have it set <envar>LD_LIBRARY_PATH</envar>
(also see the <command>Apache</command> <command>envvars</command> script, (also see the <command>Apache</command> <command>envvars</command> script,
skipping to change at line 1268 skipping to change at line 1269
<para>The default is to use <para>The default is to use
<systemitem class="library">Berkeley DB</systemitem> if it is available. <systemitem class="library">Berkeley DB</systemitem> if it is available.
If you do not want to use If you do not want to use
<systemitem class="library">Berkeley DB</systemitem> you must disable it <systemitem class="library">Berkeley DB</systemitem> you must disable it
(<ulink url="#build_flag_--disable-bdb">--disable-bdb</ulink>). (<ulink url="#build_flag_--disable-bdb">--disable-bdb</ulink>).
Similar functionality is provided by the Similar functionality is provided by the
<systemitem class="library">NDBM</systemitem> library <systemitem class="library">NDBM</systemitem> library
and from <systemitem class="library">GNU GDBM</systemitem> and from <systemitem class="library">GNU GDBM</systemitem>
(versions <literal class="version">1.8.3</literal> (versions <literal class="version">1.8.3</literal>
through <literal class="version">1.18.1</literal>, through <literal class="version">1.19</literal>,
the latter being the version tested against). the latter being the version tested against).
<systemitem class="library">GNU GDBM</systemitem> must be built with its <systemitem class="library">GNU GDBM</systemitem> must be built with its
<systemitem class="library">NDBM</systemitem> compatibility mode. <systemitem class="library">NDBM</systemitem> compatibility mode.
These libraries may already be installed on your system. These libraries may already be installed on your system.
Get <systemitem class="library">GDBM</systemitem> from Get <systemitem class="library">GDBM</systemitem> from
<ulink url="ftp://ftp.gnu.org/gnu/gdbm/">ftp://ftp.gnu.org/gnu/gdbm</ulink>. <ulink url="http://ftp.gnu.org/gnu/gdbm/">http://ftp.gnu.org/gnu/gdbm</ulink>.
See the See the
<ulink url="#build_flag_--enable-ndbm">--enable-ndbm</ulink>, <ulink url="#build_flag_--enable-ndbm">--enable-ndbm</ulink>,
<ulink url="#build_flag_--with-gdbm-lib">--with-gdbm-lib</ulink>, and <ulink url="#build_flag_--with-gdbm-lib">--with-gdbm-lib</ulink>, and
<ulink url="#build_flag_--with-gdbm-lib">--with-gdbm-includes</ulink> <ulink url="#build_flag_--with-gdbm-lib">--with-gdbm-includes</ulink>
configure flags. configure flags.
</para> </para>
<note id="note3" xreflabel="Enabling dbm database support"><title>Notes</title> <note id="note3" xreflabel="Enabling dbm database support"><title>Notes</title>
<itemizedlist> <itemizedlist>
<listitem><para>It may be necessary to create (or update) links to the <listitem><para>It may be necessary to create (or update) links to the
skipping to change at line 1328 skipping to change at line 1329
<listitem><para>On some platforms, <listitem><para>On some platforms,
applications (including <command>DACS</command>) that use applications (including <command>DACS</command>) that use
<systemitem class="library">Berkeley DB</systemitem> may need to be <systemitem class="library">Berkeley DB</systemitem> may need to be
linked with the <option>-lpthread</option> flag. linked with the <option>-lpthread</option> flag.
</para></listitem> </para></listitem>
<listitem><para>Here is how we built <listitem><para>Here is how we built
<systemitem class="library">GDBM</systemitem> for <systemitem class="library">GDBM</systemitem> for
<command>DACS</command> after unpacking it: <command>DACS</command> after unpacking it:
<programlisting> <programlisting>
% ./configure --prefix=/usr/local/gdbm-1.18.1 --enable-libgdbm-compat % ./configure --prefix=/usr/local/gdbm-1.19 --enable-libgdbm-compat
% make % make
(All should go well.) (All should go well.)
% make install % make install
(All should go well here, too.) (All should go well here, too.)
</programlisting> </programlisting>
</para></listitem> </para></listitem>
<listitem><para>You cannot enable the <listitem><para>You cannot enable the
<systemitem class="library">NDBM</systemitem> library <systemitem class="library">NDBM</systemitem> library
and <systemitem class="library">GNU GDBM</systemitem>. and <systemitem class="library">GNU GDBM</systemitem>.
skipping to change at line 1374 skipping to change at line 1375
</itemizedlist> </itemizedlist>
</note> </note>
</listitem> </listitem>
<listitem id="install-sqlite"><para><application>SQLite</application></para> <listitem id="install-sqlite"><para><application>SQLite</application></para>
<para>The <ulink url="https://www.sqlite.org">SQLite</ulink> database, <para>The <ulink url="https://www.sqlite.org">SQLite</ulink> database,
which can be used together with the which can be used together with the
<ulink url="#dbm-databases">dbm-type databases</ulink>, <ulink url="#dbm-databases">dbm-type databases</ulink>,
is another option for storing is another option for storing
<command>DACS</command> configuration information. <command>DACS</command> configuration information.
Version <literal class="version">3.34.0</literal> is being used for testing Version <literal class="version">3.35.5</literal> is being used for testing
(we use the "sqlite-autoconf" amalgamation tarball). (we use the "sqlite-autoconf" amalgamation tarball).
See the <command>DACS</command> configure arguments: See the <command>DACS</command> configure arguments:
<ulink url="#build_flag_--enable-sqlite">--enable-sqlite</ulink>, <ulink url="#build_flag_--enable-sqlite">--enable-sqlite</ulink>,
<ulink url="#build_flag_--disable-sqlite">--disable-sqlite</ulink>, and <ulink url="#build_flag_--disable-sqlite">--disable-sqlite</ulink>, and
<ulink url="#build_flag_--with-sqlite">--with-sqlite</ulink>. <ulink url="#build_flag_--with-sqlite">--with-sqlite</ulink>.
</para> </para>
<note id="note3.12" xreflabel="Build notes for SQlite"><title>Notes</title> <note id="note3.12" xreflabel="Build notes for SQlite"><title>Notes</title>
<para> <para>
<itemizedlist> <itemizedlist>
<listitem><para>Here is how we built
<systemitem class="library">SQlite</systemitem>:
<programlisting>
% ./configure --prefix=/usr/local/sqlite-3.35.5
% make
% make install
</programlisting>
</para></listitem>
<listitem><para>On <systemitem class="osname">FreeBSD</systemitem> at least, <listitem><para>On <systemitem class="osname">FreeBSD</systemitem> at least,
an apparent bug in the <systemitem class="library">SQlite</systemitem> an apparent bug in the <systemitem class="library">SQlite</systemitem>
build procedure can cause a compilation error. build procedure can cause a compilation error.
To avoid the error, To avoid the error, after running <command>configure</command>
edit the definition of the <symbol>DEFS</symbol> symbol edit the definition of the <symbol>DEFS</symbol> symbol
in the <filename>Makefile</filename> to remove the embedded space by in the <filename>Makefile</filename> to remove the embedded space by
changing: changing:
<programlisting> <programlisting>
-DPACKAGE_STRING=\"sqlite 3.34.0\" -DPACKAGE_STRING=\"sqlite 3.35.5\"
</programlisting> </programlisting>
to: to:
<programlisting> <programlisting>
-DPACKAGE_STRING=\"sqlite-3.34.0\" -DPACKAGE_STRING=\"sqlite-3.35.5\"
</programlisting>
</para></listitem>
<listitem><para>Here is how we built
<systemitem class="library">SQlite</systemitem>:
<programlisting>
% ./configure --prefix=/usr/local/sqlite-3.34.0
% make
% make install
</programlisting> </programlisting>
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
</para> </para>
</note> </note>
</listitem> </listitem>
<listitem id="install-libdsm"><para><command>libdsm</command></para> <listitem id="install-libdsm"><para><command>libdsm</command></para>
<para>If you want to be able to authenticate using Microsoft's <para>If you want to be able to authenticate using Microsoft's
<ulink url="https://en.wikipedia.org/wiki/Server_Message_Block">SMB</ulink>/<uli nk url="https://en.wikipedia.org/wiki/NT_LAN_Manager">NTLM</ulink> protocol <ulink url="https://en.wikipedia.org/wiki/Server_Message_Block">SMB</ulink>/<uli nk url="https://en.wikipedia.org/wiki/NT_LAN_Manager">NTLM</ulink> protocol
(see (see
<ulink url="dacs_authenticate.8.html#local_ntlm_authenticate">local_ntlm_authent icate</ulink>), <ulink url="dacs_authenticate.8.html#local_ntlm_authenticate">local_ntlm_authent icate</ulink>),
skipping to change at line 1466 skipping to change at line 1468
<note id="note39" xreflabel="Build notes for libdsm"><title>libdsm Notes</title> <note id="note39" xreflabel="Build notes for libdsm"><title>libdsm Notes</title>
<para>Although the library is currently functional <para>Although the library is currently functional
and tested, configuration of <systemitem class="library">libdsm</systemitem> and tested, configuration of <systemitem class="library">libdsm</systemitem>
is still not fully integrated within the main <command>DACS</command> build. is still not fully integrated within the main <command>DACS</command> build.
To use <systemitem class="library">libdsm</systemitem>: To use <systemitem class="library">libdsm</systemitem>:
<orderedlist> <orderedlist>
<listitem><para>Unpack the <command>DACS</command> tarfile <listitem><para>Unpack the <command>DACS</command> tarfile
</para></listitem> </para></listitem>
<listitem><para><command>chdir</command> <listitem><para><command>chdir</command>
to <literal>dacs-1.4.45/src/libdsm</literal> and to <literal>dacs-1.4.46/src/libdsm</literal> and
refer to the <filename>README</filename> in that directory for refer to the <filename>README</filename> in that directory for
detailed instructions. up-to-date, detailed instructions.
</para> </para>
<para> <para>
We continue here with a brief outline of the procedure to build the library. We continue here with a brief outline of the procedure to build the library.
If you are going to enable NTLM authentication, If you are going to enable NTLM authentication,
or think you might do so later, or think you might do so later,
build the library before running <command>configure</command> build the library before running <command>configure</command>
for <command>DACS</command>. for <command>DACS</command>.
If you do not need NTLM authentication, you need not build the library. If you do not need NTLM authentication, you need not build the library.
</para></listitem> </para></listitem>
skipping to change at line 1787 skipping to change at line 1789
<ulink url="#build_flag_--with-xmlsec1-config">--with-xmlsec1-config</ulink> <ulink url="#build_flag_--with-xmlsec1-config">--with-xmlsec1-config</ulink>
</para></listitem> </para></listitem>
<listitem id="install-openldap"><para><command>OpenLDAP</command></para> <listitem id="install-openldap"><para><command>OpenLDAP</command></para>
<para>Authentication through <acronym>LDAP</acronym> <para>Authentication through <acronym>LDAP</acronym>
or <application>Microsoft Active Directory</application> or <application>Microsoft Active Directory</application>
(see (see
<ulink url="dacs_authenticate.8.html#local_ldap_authenticate">local_ldap_authent icate</ulink>) <ulink url="dacs_authenticate.8.html#local_ldap_authenticate">local_ldap_authent icate</ulink>)
is implemented using <ulink url="https://www.openldap.org">OpenLDAP</ulink>. is implemented using <ulink url="https://www.openldap.org">OpenLDAP</ulink>.
This release of <command>DACS</command> has This release of <command>DACS</command> has
been tested only with <literal class="version">openldap-2.4.56</literal> been tested only with <literal class="version">openldap-2.5.4</literal>
and we strongly recommend that you use that version. and we strongly recommend that you use that version.
</para> </para>
<para>It is not known whether this release of <command>DACS</command> <para>It is not known whether this release of <command>DACS</command>
will work with any other will work with any other
version of <command>OpenLDAP</command> - we do not support them. version of <command>OpenLDAP</command> - we do not support them.
<command>DACS</command> may work properly <command>DACS</command> may work properly
with <command>OpenLDAP</command> versions at least as old as with <command>OpenLDAP</command> versions at least as old as
<literal class="version">2.2.24</literal>, if you really must use one of them. <literal class="version">2.2.24</literal>, if you really must use one of them.
</para> </para>
skipping to change at line 1826 skipping to change at line 1828
is installed), headers and libraries relative to the root of the specified is installed), headers and libraries relative to the root of the specified
directory will be used rather than any installed directory will be used rather than any installed
<command>OpenLDAP</command> files; it is not necessary to <command>OpenLDAP</command> files; it is not necessary to
<emphasis>install</emphasis> <command>OpenLDAP</command>, <emphasis>install</emphasis> <command>OpenLDAP</command>,
you only need to <emphasis>build</emphasis> it - you only need to <emphasis>build</emphasis> it -
so you do not need to be concerned about hassles associated with so you do not need to be concerned about hassles associated with
upgrading or any other versions that might already be installed on your upgrading or any other versions that might already be installed on your
system. system.
</para> </para>
<para>To build <command>OpenLDAP</command> for <para>To build <command>OpenLDAP</command> for <command>DACS</command>,
<command>DACS</command>, from the root of your from the root of your <command>OpenLDAP</command> distribution do:
<command>OpenLDAP</command> distribution do:
<screen> <screen>
% ./configure --with-tls=openssl --disable-slapd --enable-static \ % ./configure --with-tls=openssl --disable-slapd --enable-static \
CPPFLAGS="-I/usr/local/openssl-1.1.1i/include" \ CFLAGS="-I/usr/local/openssl-1.1.1k/include" \
LDFLAGS="-L/usr/local/openssl-1.1.1i/lib -Wl,-rpath,/usr/local/openssl-1.1.1 LDFLAGS="-L/usr/local/openssl-1.1.1k/lib -Wl,-rpath,/usr/local/openssl-1.1.1
i/lib" k/lib"
% make % make
</screen> </screen>
If so instructed, do a "<userinput>make depend</userinput>" If <command>configure</command> fails, try using <literal>CPPFLAGS</literal>
instead of <literal>CFLAGS</literal> above.
If requested, do a "<userinput>make depend</userinput>"
before the <command>make</command>. before the <command>make</command>.
</para> </para>
<para>See the <command>DACS</command> configure arguments: <para>See the <command>DACS</command> configure arguments:
<ulink url="#build_flag_--enable-ldap-auth">--enable-ldap-auth</ulink> <ulink url="#build_flag_--enable-ldap-auth">--enable-ldap-auth</ulink>
and and
<ulink url="#build_flag_--with-ldap">--with-ldap</ulink> <ulink url="#build_flag_--with-ldap">--with-ldap</ulink>
</para> </para>
</listitem> </listitem>
skipping to change at line 3296 skipping to change at line 3299
Location of <command>DACS</command> federations root directory Location of <command>DACS</command> federations root directory
(default: <filename class="directory"><replaceable>PREFIX</replaceable>/federati ons</filename>). (default: <filename class="directory"><replaceable>PREFIX</replaceable>/federati ons</filename>).
</para></listitem> </para></listitem>
</varlistentry> </varlistentry>
<varlistentry id="build_flag_--with-gdbm-includes"> <varlistentry id="build_flag_--with-gdbm-includes">
<term><option>--with-gdbm-includes</option>=<replaceable>DIR</replaceable></term > <term><option>--with-gdbm-includes</option>=<replaceable>DIR</replaceable></term >
<listitem><para>Enable ndbm support using gdbm's compatibility API <listitem><para>Enable ndbm support using gdbm's compatibility API
(<ulink url="https://directory.fsf.org/gdbm.html">gdbm(3)</ulink>), (<ulink url="https://directory.fsf.org/gdbm.html">gdbm(3)</ulink>),
specifying the include flags to use. specifying the include flags to use.
(Example: <option>--with-gdbm-includes=-I/local/src/gdbm-1.18/include</option>). (Example: <option>--with-gdbm-includes=-I/local/src/gdbm-1.19/include</option>).
(CentOS Example: <option>--with-gdbm-includes=-I/usr/include/gdbm</option>). (CentOS Example: <option>--with-gdbm-includes=-I/usr/include/gdbm</option>).
</para></listitem> </para></listitem>
</varlistentry> </varlistentry>
<varlistentry id="build_flag_--with-gdbm-lib"> <varlistentry id="build_flag_--with-gdbm-lib">
<term><option>--with-gdbm-lib</option>=<replaceable>LIB</replaceable></term> <term><option>--with-gdbm-lib</option>=<replaceable>LIB</replaceable></term>
<listitem><para>Enable ndbm support using gdbm's compatibility API <listitem><para>Enable ndbm support using gdbm's compatibility API
(<ulink url="https://directory.fsf.org/gdbm.html">gdbm(3)</ulink>), (<ulink url="https://directory.fsf.org/gdbm.html">gdbm(3)</ulink>),
specifying the link flags to use, the pathname for the library, specifying the link flags to use, the pathname for the library,
and any other necessary flags. and any other necessary flags.
(FreeBSD Example: <option>--with-gdbm-lib="-Wl,-rpath,/local/src/gdbm-1.18/lib - L/local/src/gdbm-1.18/lib -lgdbm"</option>). (FreeBSD Example: <option>--with-gdbm-lib="-Wl,-rpath,/local/src/gdbm-1.19/lib - L/local/src/gdbm-1.19/lib -lgdbm"</option>).
(CentOS Example: <option>--with-gdbm-lib="-L/usr/lib64 -lgdbm"</option>). (CentOS Example: <option>--with-gdbm-lib="-L/usr/lib64 -lgdbm"</option>).
</para></listitem> </para></listitem>
</varlistentry> </varlistentry>
<varlistentry id="build_flag_--with-htdocs"> <varlistentry id="build_flag_--with-htdocs">
<term><option>--with-htdocs=<replaceable>DIR</replaceable></option></term> <term><option>--with-htdocs=<replaceable>DIR</replaceable></option></term>
<listitem><para>Location of <command>Apache</command> <command>DACS</command> <listitem><para>Location of <command>Apache</command> <command>DACS</command>
files if not the <filename class="directory">htdocs</filename> subdirectory files if not the <filename class="directory">htdocs</filename> subdirectory
of the <command>Apache</command> install directory. of the <command>Apache</command> install directory.
</para></listitem> </para></listitem>
skipping to change at line 3358 skipping to change at line 3361
JDK include directories JDK include directories
(Example: <option>--with-jdk-includes="-I/usr/local/jdk/include -I/usr/local/jdk /include/freebsd"</option>). (Example: <option>--with-jdk-includes="-I/usr/local/jdk/include -I/usr/local/jdk /include/freebsd"</option>).
</para></listitem> </para></listitem>
</varlistentry> </varlistentry>
<varlistentry id="build_flag_--with-ldap"> <varlistentry id="build_flag_--with-ldap">
<term><option>--with-ldap=<replaceable>DIR</replaceable></option></term> <term><option>--with-ldap=<replaceable>DIR</replaceable></option></term>
<listitem><para>Location of <command>OpenLDAP</command> <listitem><para>Location of <command>OpenLDAP</command>
<emphasis>source</emphasis> files. <emphasis>source</emphasis> files.
This is the root directory for the OpenLDAP source distribution This is the root directory for the OpenLDAP source distribution
(Example: <filename class="directory">/local/src/openldap-2.4.56</filename>). (Example: <filename class="directory">/local/src/openldap-2.5.4</filename>).
This implies <option>--enable-ldap-auth</option>. This implies <option>--enable-ldap-auth</option>.
</para></listitem> </para></listitem>
</varlistentry> </varlistentry>
<varlistentry id="build_flag_--with-libdsm"> <varlistentry id="build_flag_--with-libdsm">
<term><option>--with-libdsm=<replaceable>DIR</replaceable></option></term> <term><option>--with-libdsm=<replaceable>DIR</replaceable></option></term>
<listitem><para>Location of the <listitem><para>Location of the
<systemitem class="library">libdsm</systemitem> library <systemitem class="library">libdsm</systemitem> library
(which will be used instead of Samba). (which will be used instead of Samba).
This is the root directory of the library's source distribution. This is the root directory of the library's source distribution.
 End of changes. 37 change blocks. 
57 lines changed or deleted 61 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)