diff --git a/doc/Makefile b/doc/Makefile
index a7ea171f2..b6235a2db 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -35,6 +35,7 @@ clean:
rm -f *.out
rm -f *.pdf
rm -f *.toc
+ rm -f version.tex
[ ! -f contributed_modules.tex ] || rm contributed_modules.tex
distclean: clean
diff --git a/doc/dev.html b/doc/dev.html
deleted file mode 100644
index 9360a7987..000000000
--- a/doc/dev.html
+++ /dev/null
@@ -1,412 +0,0 @@
-
-
-
-Ejabberd 3.0.0-prealpha Developers Guide
-
-
-
-
-
-
-
-
-
-
-
Ejabberd 3.0.0-prealpha Developers Guide |
-
-
-
-
-
-
I can thoroughly recommend ejabberd for ease of setup –
-Kevin Smith, Current maintainer of the Psi project
-Contents
Introduction
-
ejabberd is a free and open source instant messaging server written in Erlang/OTP.
ejabberd is cross-platform, distributed, fault-tolerant, and based on open standards to achieve real-time communication.
ejabberd is designed to be a rock-solid and feature rich XMPP server.
ejabberd is suitable for small deployments, whether they need to be scalable or not, as well as extremely big deployments.
-1 Key Features
-
-
ejabberd is:
-
-
-Cross-platform: ejabberd runs under Microsoft Windows and Unix derived systems such as Linux, FreeBSD and NetBSD.
- Distributed: You can run ejabberd on a cluster of machines and all of them will serve the same Jabber domain(s). When you need more capacity you can simply add a new cheap node to your cluster. Accordingly, you do not need to buy an expensive high-end machine to support tens of thousands concurrent users.
- Fault-tolerant: You can deploy an ejabberd cluster so that all the information required for a properly working service will be replicated permanently on all nodes. This means that if one of the nodes crashes, the others will continue working without disruption. In addition, nodes also can be added or replaced ‘on the fly’.
- Administrator Friendly: ejabberd is built on top of the Open Source Erlang. As a result you do not need to install an external database, an external web server, amongst others because everything is already included, and ready to run out of the box. Other administrator benefits include:
-
-
-Comprehensive documentation.
-
- Straightforward installers for Linux, Mac OS X, and Windows.
- Web Administration.
-
- Shared Roster Groups.
-
- Command line administration tool.
- Can integrate with existing authentication mechanisms.
-
- Capability to send announce messages.
-
- Internationalized: ejabberd leads in internationalization. Hence it is very well suited in a globalized world. Related features are:
-
-
-Translated to 24 languages.
- Support for IDNA.
-
- Open Standards: ejabberd is the first Open Source Jabber server claiming to fully comply to the XMPP standard.
-
-2 Additional Features
-
-
Moreover, ejabberd comes with a wide range of other state-of-the-art features:
-
-
-Modular
-
-
-Load only the modules you want.
-
- Extend ejabberd with your own custom modules.
-
- - Security
-
-
-SASL and STARTTLS for c2s and s2s connections.
-
- STARTTLS and Dialback s2s connections.
-
- Web Admin accessible via HTTPS secure access.
-
- - Databases
-
-
-Internal database for fast deployment (Mnesia).
-
- Native MySQL support.
-
- Native PostgreSQL support.
-
- ODBC data storage support.
-
- Microsoft SQL Server support.
- - Authentication
-
-
-Internal Authentication.
-
- PAM, LDAP and ODBC.
- External Authentication script.
-
- - Others
-
-
-Support for virtual hosting.
-
- Compressing XML streams with Stream Compression (XEP-0138).
-
- Statistics via Statistics Gathering (XEP-0039).
-
- IPv6 support both for c2s and s2s connections.
-
- Multi-User Chat module with support for clustering and HTML logging.
- Users Directory based on users vCards.
-
- Publish-Subscribe component with support for Personal Eventing via Pubsub.
-
- Support for web clients: HTTP Polling and HTTP Binding (BOSH) services.
-
- Component support: interface with networks such as AIM, ICQ and MSN installing special tranports.
-
-
-3 How it Works
-
A XMPP domain is served by one or more ejabberd nodes. These nodes can
-be run on different machines that are connected via a network. They all must
-have the ability to connect to port 4369 of all another nodes, and must have
-the same magic cookie (see Erlang/OTP documentation, in other words the file
-~ejabberd/.erlang.cookie must be the same on all nodes). This is
-needed because all nodes exchange information about connected users, S2S
-connections, registered services, etc…
Each ejabberd node have following modules:
-
-
-router;
-
- local router.
-
- session manager;
-
- S2S manager;
-
-3.1 Router
This module is the main router of XMPP packets on each node. It routes
-them based on their destinations domains. It has two tables: local and global
-routes. First, domain of packet destination searched in local table, and if it
-found, then the packet is routed to appropriate process. If no, then it
-searches in global table, and is routed to the appropriate ejabberd node or
-process. If it does not exists in either tables, then it sent to the S2S
-manager.
-3.2 Local Router
This module routes packets which have a destination domain equal to this server
-name. If destination JID has a non-empty user part, then it routed to the
-session manager, else it is processed depending on it’s content.
-3.3 Session Manager
This module routes packets to local users. It searches for what user resource
-packet must be sended via presence table. If this resource is connected to
-this node, it is routed to C2S process, if it connected via another node, then
-the packet is sent to session manager on that node.
-3.4 S2S Manager
This module routes packets to other XMPP servers. First, it checks if an
-open S2S connection from the domain of the packet source to the domain of
-packet destination already exists. If it is open on another node, then it
-routes the packet to S2S manager on that node, if it is open on this node, then
-it is routed to the process that serves this connection, and if a connection
-does not exist, then it is opened and registered.
-4 Authentication
-
-
-
The external authentication script follows
-the erlang port driver API.
That script is supposed to do theses actions, in an infinite loop:
-
-
-read from stdin: AABBBBBBBBB.....
-
-
-A: 2 bytes of length data (a short in network byte order)
-
- B: a string of length found in A that contains operation in plain text
-operation are as follows:
-
-
-auth:User:Server:Password (check if a username/password pair is correct)
-
- isuser:User:Server (check if it’s a valid user)
-
- setpass:User:Server:Password (set user’s password)
-
- tryregister:User:Server:Password (try to register an account)
-
- removeuser:User:Server (remove this account)
-
- removeuser3:User:Server:Password (remove this account if the password is correct)
-
-
- - write to stdout: AABB
-
-
-A: the number 2 (coded as a short, which is bytes length of following result)
-
- B: the result code (coded as a short), should be 1 for success/valid, or 0 for failure/invalid
-
-
Example python script
-
#!/usr/bin/python
-
-import sys
-from struct import *
-
-def from_ejabberd():
- input_length = sys.stdin.read(2)
- (size,) = unpack('>h', input_length)
- return sys.stdin.read(size).split(':')
-
-def to_ejabberd(bool):
- answer = 0
- if bool:
- answer = 1
- token = pack('>hh', 2, answer)
- sys.stdout.write(token)
- sys.stdout.flush()
-
-def auth(username, server, password):
- return True
-
-def isuser(username, server):
- return True
-
-def setpass(username, server, password):
- return True
-
-while True:
- data = from_ejabberd()
- success = False
- if data[0] == "auth":
- success = auth(data[1], data[2], data[3])
- elif data[0] == "isuser":
- success = isuser(data[1], data[2])
- elif data[0] == "setpass":
- success = setpass(data[1], data[2], data[3])
- to_ejabberd(success)
-
-5 XML Representation
-
Each XML stanza is represented as the following tuple:
-
XMLElement = {xmlelement, Name, Attrs, [ElementOrCDATA]}
- Name = string()
- Attrs = [Attr]
- Attr = {Key, Val}
- Key = string()
- Val = string()
- ElementOrCDATA = XMLElement | CDATA
- CDATA = {xmlcdata, string()}
-E. g. this stanza:
-
<message to='test@conference.example.org' type='groupchat'>
- <body>test</body>
-</message>
-
is represented as the following structure:
-
{xmlelement, "message",
- [{"to", "test@conference.example.org"},
- {"type", "groupchat"}],
- [{xmlelement, "body",
- [],
- [{xmlcdata, "test"}]}]}}
-
-6 Module xml
-
-
-
element_to_string(El) -> string()
-El = XMLElement
-
Returns string representation of XML stanza El.crypt(S) -> string()
-S = string()
-
Returns string which correspond to S with encoded XML special
-characters.remove_cdata(ECList) -> EList
-ECList = [ElementOrCDATA]
-EList = [XMLElement]
-
EList is a list of all non-CDATA elements of ECList.get_path_s(El, Path) -> Res
-El = XMLElement
-Path = [PathItem]
-PathItem = PathElem | PathAttr | PathCDATA
-PathElem = {elem, Name}
-PathAttr = {attr, Name}
-PathCDATA = cdata
-Name = string()
-Res = string() | XMLElement
-If Path is empty, then returns El. Else sequentially
-consider elements of Path. Each element is one of:
--
-
{elem, Name} Name is name of subelement of
-El, if such element exists, then this element considered in
-following steps, else returns empty string.
-{attr, Name} If El have attribute Name, then
-returns value of this attribute, else returns empty string.
-cdata Returns CDATA of El.
-
- TODO:
-
get_cdata/1, get_tag_cdata/1
- get_attr/2, get_attr_s/2
- get_tag_attr/2, get_tag_attr_s/2
- get_subtag/2
-
-7 Module xml_stream
-
-
-
parse_element(Str) -> XMLElement | {error, Err}
-Str = string()
-Err = term()
-
Parses Str using XML parser, returns either parsed element or error
-tuple.
-
-8 Modules
-
-8.1 Module gen_iq_handler
-
The module gen_iq_handler allows to easily write handlers for IQ packets
-of particular XML namespaces that addressed to server or to users bare JIDs.
In this module the following functions are defined:
-
-
-
add_iq_handler(Component, Host, NS, Module, Function, Type)
-Component = Module = Function = atom()
-Host = NS = string()
-Type = no_queue | one_queue | parallel
-
Registers function Module:Function as handler for IQ packets on
-virtual host Host that contain child of namespace NS in
-Component. Queueing discipline is Type. There are at least
-two components defined:
--
-
ejabberd_local Handles packets that addressed to server JID;
-ejabberd_sm Handles packets that addressed to users bare JIDs.
-
-remove_iq_handler(Component, Host, NS)
-Component = atom()
-Host = NS = string()
-
Removes IQ handler on virtual host Host for namespace NS from
-Component.
-
Handler function must have the following type:
-
-
-
Module:Function(From, To, IQ)
-From = To = jid()
-
-module(mod_cputime).
-
--behaviour(gen_mod).
-
--export([start/2,
- stop/1,
- process_local_iq/3]).
-
--include("ejabberd.hrl").
--include("jlib.hrl").
-
--define(NS_CPUTIME, "ejabberd:cputime").
-
-start(Host, Opts) ->
- IQDisc = gen_mod:get_opt(iqdisc, Opts, one_queue),
- gen_iq_handler:add_iq_handler(ejabberd_local, Host, ?NS_CPUTIME,
- ?MODULE, process_local_iq, IQDisc).
-
-stop(Host) ->
- gen_iq_handler:remove_iq_handler(ejabberd_local, Host, ?NS_CPUTIME).
-
-process_local_iq(From, To, {iq, ID, Type, XMLNS, SubEl}) ->
- case Type of
- set ->
- {iq, ID, error, XMLNS,
- [SubEl, ?ERR_NOT_ALLOWED]};
- get ->
- CPUTime = element(1, erlang:statistics(runtime))/1000,
- SCPUTime = lists:flatten(io_lib:format("~.3f", CPUTime)),
- {iq, ID, result, XMLNS,
- [{xmlelement, "query",
- [{"xmlns", ?NS_CPUTIME}],
- [{xmlelement, "cputime", [], [{xmlcdata, SCPUTime}]}]}]}
- end.
-
-8.2 Services
-
-module(mod_echo).
-
--behaviour(gen_mod).
-
--export([start/2, init/1, stop/1]).
-
--include("ejabberd.hrl").
--include("jlib.hrl").
-
-start(Host, Opts) ->
- MyHost = gen_mod:get_opt(host, Opts, "echo." ++ Host),
- register(gen_mod:get_module_proc(Host, ?PROCNAME),
- spawn(?MODULE, init, [MyHost])).
-
-init(Host) ->
- ejabberd_router:register_local_route(Host),
- loop(Host).
-
-loop(Host) ->
- receive
- {route, From, To, Packet} ->
- ejabberd_router:route(To, From, Packet),
- loop(Host);
- stop ->
- ejabberd_router:unregister_route(Host),
- ok;
- _ ->
- loop(Host)
- end.
-
-stop(Host) ->
- Proc = gen_mod:get_module_proc(Host, ?PROCNAME),
- Proc ! stop,
- {wait, Proc}.
-
-
-
-
-
This document was translated from LATEX by
-HEVEA.
-
diff --git a/doc/features.html b/doc/features.html
deleted file mode 100644
index 62f98324d..000000000
--- a/doc/features.html
+++ /dev/null
@@ -1,131 +0,0 @@
-
-
-
-Ejabberd 3.0.0-prealpha Feature Sheet
-
-
-
-
-
-
-
-
-
-
-
Ejabberd 3.0.0-prealpha Feature Sheet |
-
-
-
-
-
-
I can thoroughly recommend ejabberd for ease of setup –
-Kevin Smith, Current maintainer of the Psi project
Introduction
-
I just tried out ejabberd and was impressed both by ejabberd itself and the language it is written in, Erlang. —
-Joeri
ejabberd is a free and open source instant messaging server written in Erlang/OTP.
ejabberd is cross-platform, distributed, fault-tolerant, and based on open standards to achieve real-time communication.
ejabberd is designed to be a rock-solid and feature rich XMPP server.
ejabberd is suitable for small deployments, whether they need to be scalable or not, as well as extremely big deployments.
-Key Features
-
-
Erlang seems to be tailor-made for writing stable, robust servers. —
-Peter Saint-André, Executive Director of the Jabber Software Foundation
ejabberd is:
-
-
-Cross-platform: ejabberd runs under Microsoft Windows and Unix derived systems such as Linux, FreeBSD and NetBSD.
- Distributed: You can run ejabberd on a cluster of machines and all of them will serve the same Jabber domain(s). When you need more capacity you can simply add a new cheap node to your cluster. Accordingly, you do not need to buy an expensive high-end machine to support tens of thousands concurrent users.
- Fault-tolerant: You can deploy an ejabberd cluster so that all the information required for a properly working service will be replicated permanently on all nodes. This means that if one of the nodes crashes, the others will continue working without disruption. In addition, nodes also can be added or replaced ‘on the fly’.
- Administrator Friendly: ejabberd is built on top of the Open Source Erlang. As a result you do not need to install an external database, an external web server, amongst others because everything is already included, and ready to run out of the box. Other administrator benefits include:
-
-
-Comprehensive documentation.
-
- Straightforward installers for Linux, Mac OS X, and Windows.
- Web Administration.
-
- Shared Roster Groups.
-
- Command line administration tool.
- Can integrate with existing authentication mechanisms.
-
- Capability to send announce messages.
-
- Internationalized: ejabberd leads in internationalization. Hence it is very well suited in a globalized world. Related features are:
-
-
-Translated to 24 languages.
- Support for IDNA.
-
- Open Standards: ejabberd is the first Open Source Jabber server claiming to fully comply to the XMPP standard.
-
-Additional Features
-
-
ejabberd is making inroads to solving the "buggy incomplete server" problem —
-Justin Karneges, Founder of the Psi and the Delta projects
Moreover, ejabberd comes with a wide range of other state-of-the-art features:
-
-
-Modular
-
-
-Load only the modules you want.
-
- Extend ejabberd with your own custom modules.
-
- - Security
-
-
-SASL and STARTTLS for c2s and s2s connections.
-
- STARTTLS and Dialback s2s connections.
-
- Web Admin accessible via HTTPS secure access.
-
- - Databases
-
-
-Internal database for fast deployment (Mnesia).
-
- Native MySQL support.
-
- Native PostgreSQL support.
-
- ODBC data storage support.
-
- Microsoft SQL Server support.
- - Authentication
-
-
-Internal Authentication.
-
- PAM, LDAP and ODBC.
- External Authentication script.
-
- - Others
-
-
-Support for virtual hosting.
-
- Compressing XML streams with Stream Compression (XEP-0138).
-
- Statistics via Statistics Gathering (XEP-0039).
-
- IPv6 support both for c2s and s2s connections.
-
- Multi-User Chat module with support for clustering and HTML logging.
- Users Directory based on users vCards.
-
- Publish-Subscribe component with support for Personal Eventing via Pubsub.
-
- Support for web clients: HTTP Polling and HTTP Binding (BOSH) services.
-
- Component support: interface with networks such as AIM, ICQ and MSN installing special tranports.
-
-
-
-
-
-
This document was translated from LATEX by
-HEVEA.
-
diff --git a/doc/guide.html b/doc/guide.html
deleted file mode 100644
index c242dbb77..000000000
--- a/doc/guide.html
+++ /dev/null
@@ -1,4174 +0,0 @@
-
-
-
-
-
-
-
- ejabberd 3.0.0-alpha-x
-
- Installation and Operation Guide
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-| ejabberd 3.0.0-alpha-x |
-| |
-| Installation and Operation Guide |
-
-
-
-
-
- |
-
-
-Contents
-
-
ejabberd is a free and open source instant messaging server written in Erlang/OTP.
ejabberd is cross-platform, distributed, fault-tolerant, and based on open standards to achieve real-time communication.
ejabberd is designed to be a rock-solid and feature rich XMPP server.
ejabberd is suitable for small deployments, whether they need to be scalable or not, as well as extremely big deployments.
-1.1 Key Features
-
-
ejabberd is:
-
-
-Cross-platform: ejabberd runs under Microsoft Windows and Unix derived systems such as Linux, FreeBSD and NetBSD.
- Distributed: You can run ejabberd on a cluster of machines and all of them will serve the same Jabber domain(s). When you need more capacity you can simply add a new cheap node to your cluster. Accordingly, you do not need to buy an expensive high-end machine to support tens of thousands concurrent users.
- Fault-tolerant: You can deploy an ejabberd cluster so that all the information required for a properly working service will be replicated permanently on all nodes. This means that if one of the nodes crashes, the others will continue working without disruption. In addition, nodes also can be added or replaced ‘on the fly’.
- Administrator Friendly: ejabberd is built on top of the Open Source Erlang. As a result you do not need to install an external database, an external web server, amongst others because everything is already included, and ready to run out of the box. Other administrator benefits include:
-
-
-Comprehensive documentation.
-
- Straightforward installers for Linux, Mac OS X, and Windows.
- Web Administration.
-
- Shared Roster Groups.
-
- Command line administration tool.
- Can integrate with existing authentication mechanisms.
-
- Capability to send announce messages.
-
- Internationalized: ejabberd leads in internationalization. Hence it is very well suited in a globalized world. Related features are:
-
-
-Translated to 24 languages.
- Support for IDNA.
-
- Open Standards: ejabberd is the first Open Source Jabber server claiming to fully comply to the XMPP standard.
-
-1.2 Additional Features
-
-
Moreover, ejabberd comes with a wide range of other state-of-the-art features:
-
-
-Modular
-
-
-Load only the modules you want.
-
- Extend ejabberd with your own custom modules.
-
- - Security
-
-
-SASL and STARTTLS for c2s and s2s connections.
-
- STARTTLS and Dialback s2s connections.
-
- Web Admin accessible via HTTPS secure access.
-
- - Databases
-
-
-Internal database for fast deployment (Mnesia).
-
- Native MySQL support.
-
- Native PostgreSQL support.
-
- ODBC data storage support.
-
- Microsoft SQL Server support.
- - Authentication
-
-
-Internal Authentication.
-
- PAM, LDAP and ODBC.
- External Authentication script.
-
- - Others
-
-
-Support for virtual hosting.
-
- Compressing XML streams with Stream Compression (XEP-0138).
-
- Statistics via Statistics Gathering (XEP-0039).
-
- IPv6 support both for c2s and s2s connections.
-
- Multi-User Chat module with support for clustering and HTML logging.
- Users Directory based on users vCards.
-
- Publish-Subscribe component with support for Personal Eventing via Pubsub.
-
- Support for web clients: HTTP Polling and HTTP Binding (BOSH) services.
-
- Component support: interface with networks such as AIM, ICQ and MSN installing special tranports.
-
-
-
-
Probably the easiest way to install an ejabberd instant messaging server
-is using the binary installer published by ProcessOne.
-The binary installers of released ejabberd versions
-are available in the ProcessOne ejabberd downloads page:
-http://www.process-one.net/en/ejabberd/downloads
The installer will deploy and configure a full featured ejabberd
-server and does not require any extra dependencies.
In *nix systems, remember to set executable the binary installer before starting it. For example:
-
chmod +x ejabberd-2.0.0_1-linux-x86-installer.bin
-./ejabberd-2.0.0_1-linux-x86-installer.bin
-
ejabberd can be started manually at any time,
-or automatically by the operating system at system boot time.
To start and stop ejabberd manually,
-use the desktop shortcuts created by the installer.
-If the machine doesn’t have a graphical system, use the scripts ’start’
-and ’stop’ in the ’bin’ directory where ejabberd is installed.
The Windows installer also adds ejabberd as a system service,
-and a shortcut to a debug console for experienced administrators.
-If you want ejabberd to be started automatically at boot time,
-go to the Windows service settings and set ejabberd to be automatically started.
-Note that the Windows service is a feature still in development,
-and for example it doesn’t read the file ejabberdctl.cfg.
On a *nix system, if you want ejabberd to be started as daemon at boot time,
-copy ejabberd.init from the ’bin’ directory to something like /etc/init.d/ejabberd
-(depending on your distribution).
-Create a system user called ejabberd;
-it will be used by the script to start the server.
-Then you can call /etc/inid.d/ejabberd start as root to start the server.
If ejabberd doesn’t start correctly in Windows,
-try to start it using the shortcut in desktop or start menu.
-If the window shows error 14001, the solution is to install:
-"Microsoft Visual C++ 2005 SP1 Redistributable Package".
-You can download it from
-www.microsoft.com.
-Then uninstall ejabberd and install it again.
If ejabberd doesn’t start correctly and a crash dump is generated,
-there was a severe problem.
-You can try starting ejabberd with
-the script bin/live.bat in Windows,
-or with the command bin/ejabberdctl live in other Operating Systems.
-This way you see the error message provided by Erlang
-and can identify what is exactly the problem.
The ejabberdctl administration script is included in the bin directory.
-Please refer to the section 4.1 for details about ejabberdctl,
-and configurable options to fine tune the Erlang runtime system.
-
Some Operating Systems provide a specific ejabberd package adapted to
-the system architecture and libraries.
-It usually also checks dependencies
-and performs basic configuration tasks like creating the initial
-administrator account. Some examples are Debian and Gentoo. Consult the
-resources provided by your Operating System for more information.
Usually those packages create a script like /etc/init.d/ejabberd
-to start and stop ejabberd as a service at boot time.
-
CEAN
-(Comprehensive Erlang Archive Network) is a repository that hosts binary
-packages from many Erlang programs, including ejabberd and all its dependencies.
-The binaries are available for many different system architectures, so this is an
-alternative to the binary installer and Operating System’s ejabberd packages.
You will have to create your own ejabberd start
-script depending of how you handle your CEAN installation.
-The default ejabberdctl script is located
-into ejabberd’s priv directory and can be used as an example.
-
-
The canonical form for distribution of ejabberd stable releases is the source code package.
-Compiling ejabberd from source code is quite easy in *nix systems,
-as long as your system have all the dependencies.
-
-
To compile ejabberd on a ‘Unix-like’ operating system, you need:
-
-
-GNU Make
-
- GCC
-
- Erlang/OTP R12B-5 or higher.
-
- exmpp 0.9.6 or higher
-
- OpenSSL 0.9.8 or higher, for STARTTLS, SASL and SSL encryption.
-
- Zlib 1.2.3 or higher, for Stream Compression support (XEP-0138). Optional.
-
- Erlang mysql library. Optional. For MySQL authentication or storage. See section 3.2.1.
-
- Erlang pgsql library. Optional. For PostgreSQL authentication or storage. See section 3.2.3.
-
- PAM library. Optional. For Pluggable Authentication Modules (PAM). See section 3.1.4.
-
- ESASL library. Optional. For SASL GSSAPI authentication. See section 3.1.4.
-
- ImageMagick’s Convert program. Optional. For CAPTCHA challenges. See section 3.1.8.
-
-
-
Released versions of ejabberd are available in the ProcessOne ejabberd downloads page:
-http://www.process-one.net/en/ejabberd/downloads
-Alternatively, the latest development source code can be retrieved from the Git repository using the commands:
-
git clone git://git.process-one.net/ejabberd/mainline.git ejabberd
-cd ejabberd
-
-
-
To compile ejabberd execute the commands:
-
./configure
-make
-
The build configuration script allows several options.
-To get the full list run the command:
-
./configure --help
-
Some options that you may be interested in modifying:
-
-
- --prefix=/
-
- Specify the path prefix where the files will be copied when running
- the make install command.
- --enable-user[=USER]
-
- Allow this normal system user to execute the ejabberdctl script
- (see section 4.1),
- read the configuration files,
- read and write in the spool directory,
- read and write in the log directory.
- The account user and group must exist in the machine
- before running make install.
- This account doesn’t need an explicit HOME directory, because
- /var/lib/ejabberd/ will be used by default.
- --enable-pam
-
- Enable the PAM authentication method (see section 3.1.4).
- --enable-odbc or --enable-mssql
-
- Required if you want to use an external database.
- See section 3.2 for more information.
- --enable-full-xml
-
- Enable the use of XML based optimisations.
- It will for example use CDATA to escape characters in the XMPP stream.
- Use this option only if you are sure your XMPP clients include a fully compliant XML parser.
- --disable-transient-supervisors
-
- Disable the use of Erlang/OTP supervision for transient processes.
-
-
-
To install ejabberd in the destination directories, run the command:
-
make install
-
Note that you probably need administrative privileges in the system
-to install ejabberd.
The files and directories created are, by default:
-
-
- /etc/ejabberd/
- Configuration directory:
-
-
- ejabberd.cfg
- ejabberd configuration file
-
- ejabberdctl.cfg
- Configuration file of the administration script
-
- inetrc
- Network DNS configuration file
-
- - /lib/ejabberd/
-
-
-
- ebin/
- Erlang binary files (*.beam)
-
- include/
- Erlang header files (*.hrl)
-
- priv/
- Additional files required at runtime
-
-
- bin/
- Executable programs
-
- lib/
- Binary system libraries (*.so)
-
- msgs/
- Translation files (*.msgs)
-
-
- - /sbin/ejabberdctl
- Administration script (see section 4.1)
-
- /share/doc/ejabberd/
- Documentation of ejabberd
-
- /var/lib/ejabberd/
- Spool directory:
-
-
- .erlang.cookie
- Erlang cookie file (see section 5.3)
-
- acl.DCD, ...
- Mnesia database spool files (*.DCD, *.DCL, *.DAT)
-
- - /var/log/ejabberd/
- Log directory (see section 7.1):
-
-
- ejabberd.log
- ejabberd service log
-
- erlang.log
- Erlang/OTP system log
-
-
-
-
You can use the ejabberdctl command line administration script to start and stop ejabberd.
-If you provided the configure option --enable-user=USER (see 2.4.3),
-you can execute ejabberdctl with either that system account or root.
Usage example:
-
ejabberdctl start
-
-ejabberdctl status
-The node ejabberd@localhost is started with status: started
-ejabberd is running in that node
-
-ejabberdctl stop
-
If ejabberd doesn’t start correctly and a crash dump is generated,
-there was a severe problem.
-You can try starting ejabberd with
-the command ejabberdctl live
-to see the error message provided by Erlang
-and can identify what is exactly the problem.
Please refer to the section 4.1 for details about ejabberdctl,
-and configurable options to fine tune the Erlang runtime system.
If you want ejabberd to be started as daemon at boot time,
-copy ejabberd.init to something like /etc/init.d/ejabberd
-(depending on your distribution).
-Create a system user called ejabberd;
-it will be used by the script to start the server.
-Then you can call /etc/inid.d/ejabberd start as root to start the server.
-
-
The command to compile ejabberd in BSD systems is:
-
gmake
-
-
-
You need to have GNU install,
-but it isn’t included in Solaris.
-It can be easily installed if your Solaris system
-is set up for blastwave.org
-package repository.
-Make sure /opt/csw/bin is in your PATH and run:
-
pkg-get -i fileutils
-
If that program is called ginstall,
-modify the ejabberd Makefile script to suit your system,
-for example:
-
cat Makefile | sed s/install/ginstall/ > Makefile.gi
-
And finally install ejabberd with:
-
gmake -f Makefile.gi ginstall
-
-
-
-
To compile ejabberd on a Microsoft Windows system, you need:
-
-
We assume that we will try to put as much library as possible into C:\sdk\ to make it easier to track what is install for ejabberd.
-
-Install Erlang emulator (for example, into
C:\sdk\erl5.6.5).
- - Install OpenSSL in
C:\sdk\OpenSSL and add C:\sdk\OpenSSL\lib\VC to your path or copy the binaries to your system directory.
- - Install ZLib in
C:\sdk\gnuWin32. Copy
-C:\sdk\GnuWin32\bin\zlib1.dll to your system directory.
- - Make sure the you can access Erlang binaries from your path. For example:
set PATH=%PATH%;"C:\sdk\erl5.6.5\bin"
- - Depending on how you end up actually installing the library you might need to check and tweak the paths in the file configure.erl.
-
- While in the directory
ejabberd\src run:
-configure.bat
-nmake -f Makefile.win32
-
- Edit the file
ejabberd\src\ejabberd.cfg and run
-werl -s ejabberd -name ejabberd
-
-
You need a XMPP account and grant him administrative privileges
-to enter the ejabberd Web Admin:
-
-
-Register a XMPP account on your ejabberd server, for example admin1@example.org.
-There are two ways to register a XMPP account:
-
-
-Using ejabberdctl (see section 4.1):
-
ejabberdctl register admin1 example.org FgT5bk3
-
- Using a XMPP client and In-Band Registration (see section 3.3.18).
-
- - Edit the ejabberd configuration file to give administration rights to the XMPP account you created:
-
{acl, admins, {user, "admin1", "example.org"}}.
-{access, configure, [{allow, admins}]}.
-You can grant administrative privileges to many XMPP accounts,
-and also to accounts in other XMPP servers.
- - Restart ejabberd to load the new configuration.
-
- Open the Web Admin (
http://server:port/admin/) in your
-favourite browser. Make sure to enter the full JID as username (in this
-example: admin1@example.org. The reason that you also need to enter the
-suffix, is because ejabberd’s virtual hosting support.
-
-
To upgrade an ejabberd installation to a new version,
-simply uninstall the old version, and then install the new one.
-Of course, it is important that the configuration file
-and Mnesia database spool directory are not removed.
ejabberd automatically updates the Mnesia table definitions at startup when needed.
-If you also use an external database for storage of some modules,
-check if the release notes of the new ejabberd version
-indicates you need to also update those tables.
-
-
-
The configuration file will be loaded the first time you start ejabberd. The
-content from this file will be parsed and stored in the internal ejabberd database. Subsequently the
-configuration will be loaded from the database and any commands in the
-configuration file are appended to the entries in the database.
Note that ejabberd never edits the configuration file.
-So, the configuration changes done using the Web Admin
-are stored in the database, but are not reflected in the configuration file.
-If you want those changes to be use after ejabberd restart, you can either
-edit the configuration file, or remove all its content.
The configuration file contains a sequence of Erlang terms. Lines beginning with a
-‘%’ sign are ignored. Each term is a tuple of which the first element is
-the name of an option, and any further elements are that option’s values. If the
-configuration file do not contain for instance the ‘hosts’ option, the old
-host name(s) stored in the database will be used.
You can override the old values stored in the database by adding next lines to
-the beginning of the configuration file:
-
override_global.
-override_local.
-override_acls.
-
With these lines the old global options (shared between all ejabberd nodes in a
-cluster), local options (which are specific for this particular ejabberd node)
-and ACLs will be removed before new ones are added.
-
-
The option hosts defines a list containing one or more domains that
-ejabberd will serve.
The syntax is:
-
- {hosts, [HostName, ...]}.
Examples:
-
-
-Serving one domain:
-
{hosts, ["example.org"]}.
- - Serving three domains:
-
{hosts, ["example.net", "example.com", "jabber.somesite.org"]}.
-
-
-
Options can be defined separately for every virtual host using the
-host_config option.
The syntax is:
-
- {host_config, HostName, [Option, ...]}
Examples:
-
-
-Domain example.net is using the internal authentication method while
-domain example.com is using the LDAP server running on the
-domain localhost to perform authentication:
-
{host_config, "example.net", [{auth_method, storage},
- {auth_storage, mnesia}]}.
-
-{host_config, "example.com", [{auth_method, ldap],
- {ldap_servers, ["localhost"]},
- {ldap_uids, [{"uid"}]},
- {ldap_rootdn, "dc=localdomain"},
- {ldap_rootdn, "dc=example,dc=com"},
- {ldap_password, ""}]}.
- - Domain example.net is using ODBC to perform authentication
-while domain example.com is using the LDAP servers running on the domains
-localhost and otherhost:
-
{host_config, "example.net", [{auth_method, storage},
- {auth_storage, odbc},
- {odbc_server, "DSN=ejabberd;UID=ejabberd;PWD=ejabberd"}]}.
-
-{host_config, "example.com", [{auth_method, ldap},
- {ldap_servers, ["localhost", "otherhost"]},
- {ldap_uids, [{"uid"}]},
- {ldap_rootdn, "dc=localdomain"},
- {ldap_rootdn, "dc=example,dc=com"},
- {ldap_password, ""}]}.
-
To define specific ejabberd modules in a virtual host,
-you can define the global modules option with the common modules,
-and later add specific modules to certain virtual hosts.
-To accomplish that, instead of defining each option in host_config with the general syntax
-
- {OptionName, OptionValue}
-use this syntax:
-
- {{add, OptionName}, OptionValue}
In this example three virtual hosts have some similar modules, but there are also
-other different modules for some specific virtual hosts:
-
%% This ejabberd server has three vhosts:
-{hosts, ["one.example.org", "two.example.org", "three.example.org"]}.
-
-%% Configuration of modules that are common to all vhosts
-{modules,
- [
- {mod_roster, []},
- {mod_configure, []},
- {mod_disco, []},
- {mod_private, []},
- {mod_time, []},
- {mod_last, []},
- {mod_version, []}
- ]}.
-
-%% Add some modules to vhost one:
-{host_config, "one.example.org",
- [{{add, modules}, [
- {mod_echo, [{host, "echo-service.one.example.org"}]}
- {mod_http_bind, []},
- {mod_logxml, []}
- ]
- }
- ]}.
-
-%% Add a module just to vhost two:
-{host_config, "two.example.org",
- [{{add, modules}, [
- {mod_echo, [{host, "mirror.two.example.org"}]}
- ]
- }
- ]}.
-
-
-
The option listen defines for which ports, addresses and network protocols ejabberd
-will listen and what services will be run on them. Each element of the list is a
-tuple with the following elements:
-
-
-Port number. Optionally also the IP address and/or a transport protocol.
-
- Listening module that serves this port.
-
- Options for the TCP socket and for the listening module.
-
The option syntax is:
-
- {listen, [Listener, ...]}.
To define a listener there are several syntax.
-
- {PortNumber, Module, [Option, ...]}
- {{PortNumber, IPaddress}, Module, [Option, ...]}
- {{PortNumber, TransportProtocol}, Module, [Option, ...]}
- {{PortNumber, IPaddress, TransportProtocol}, Module, [Option, ...]}
-
The port number defines which port to listen for incoming connections.
-It can be a Jabber/XMPP standard port
-(see section 5.1) or any other valid port number.
The IP address can be represented with a string
-or an Erlang tuple with decimal or hexadecimal numbers.
-The socket will listen only in that network interface.
-It is possible to specify a generic address,
-so ejabberd will listen in all addresses.
-Depending in the type of the IP address, IPv4 or IPv6 will be used.
-When not specified the IP address, it will listen on all IPv4 network addresses.
Some example values for IP address:
-
-
-
"0.0.0.0" to listen in all IPv4 network interfaces. This is the default value when no IP is specified.
- "::" to listen in all IPv6 network interfaces
-"10.11.12.13" is the IPv4 address 10.11.12.13
-"::FFFF:127.0.0.1" is the IPv6 address ::FFFF:127.0.0.1/128
-{10, 11, 12, 13} is the IPv4 address 10.11.12.13
-{0, 0, 0, 0, 0, 65535, 32512, 1} is the IPv6 address ::FFFF:127.0.0.1/128
-{16#fdca, 16#8ab6, 16#a243, 16#75ef, 0, 0, 0, 1} is the IPv6 address FDCA:8AB6:A243:75EF::1/128
-
The transport protocol can be tcp or udp.
-Default is tcp.
-
-The available modules, their purpose and the options allowed by each one are:
-
-
-ejabberd_c2s
-
-Handles c2s connections.
- Options: access, certfile, max_fsm_queue,
-max_stanza_size, shaper,
-starttls, starttls_required, tls,
-zlib
- - ejabberd_s2s_in
-
-Handles incoming s2s connections.
- Options: max_stanza_size, shaper
- - ejabberd_service
-
-Interacts with an external component
-(as defined in the Jabber Component Protocol (XEP-0114).
- Options: access, hosts, max_fsm_queue,
-service_check_from, shaper
- - ejabberd_stun
-
-Handles STUN Binding requests as defined in
-RFC 5389.
- Options: certfile
- - ejabberd_http
-
-Handles incoming HTTP connections.
- Options: captcha, certfile, http_bind, http_poll,
-request_handlers, tls, web_admin
-
-
This is a detailed description of each option allowed by the listening modules:
-
-
-{access, AccessName}
- This option defines
-access to the port. The default value is all.
-
- {backlog, Value}
- The backlog value
-defines the maximum length that the queue of pending connections may
-grow to. This should be increased if the server is going to handle
-lots of new incoming connections as they may be dropped if there is
-no space in the queue (and ejabberd was not able to accept them
-immediately). Default value is 5.
-
- captcha
-
-Simple web page that allows a user to fill a CAPTCHA challenge (see section 3.1.8).
-
- {certfile, Path}
- Full path to a file containing the default SSL certificate.
-To define a certificate file specific for a given domain, use the global option domain_certfile.
-
- {hosts, [Hostname, ...], [HostOption, ...]}
-
-The external Jabber component that connects to this ejabberd_service
-can serve one or more hostnames.
-As HostOption you can define options for the component;
-currently the only allowed option is the password required to the component
-when attempt to connect to ejabberd: {password, Secret}.
-Note that you cannot define in a single ejabberd_service components of
-different services: add an ejabberd_service for each service,
-as seen in an example below.
-
- http_bind
-
-This option enables HTTP Binding (XEP-0124 and XEP-0206) support. HTTP Bind
-enables access via HTTP requests to ejabberd from behind firewalls which
-do not allow outgoing sockets on port 5222.
Remember that you must also install and enable the module mod_http_bind.
If HTTP Bind is enabled, it will be available at
-http://server:port/http-bind/. Be aware that support for HTTP Bind
-is also needed in the XMPP client. Remark also that HTTP Bind can be
-interesting to host a web-based XMPP client such as
-JWChat
-(check the tutorials to install JWChat with ejabberd and an
-embedded local web server
-or Apache).
-
- http_poll
-
-This option enables HTTP Polling (XEP-0025) support. HTTP Polling
-enables access via HTTP requests to ejabberd from behind firewalls which
-do not allow outgoing sockets on port 5222.
If HTTP Polling is enabled, it will be available at
-http://server:port/http-poll/. Be aware that support for HTTP Polling
-is also needed in the XMPP client. Remark also that HTTP Polling can be
-interesting to host a web-based XMPP client such as
-JWChat.
The maximum period of time to keep a client session active without
-an incoming POST request can be configured with the global option
-http_poll_timeout. The default value is five minutes.
-The option can be defined in ejabberd.cfg, expressing the time
-in seconds: {http_poll_timeout, 300}.
-
- {max_fsm_queue, Size}
-
-This option specifies the maximum number of elements in the queue of the FSM
-(Finite State Machine).
-Roughly speaking, each message in such queues represents one XML
-stanza queued to be sent into its relevant outgoing stream. If queue size
-reaches the limit (because, for example, the receiver of stanzas is too slow),
-the FSM and the corresponding connection (if any) will be terminated
-and error message will be logged.
-The reasonable value for this option depends on your hardware configuration.
-However, there is no much sense to set the size above 1000 elements.
-This option can be specified for ejabberd_service and
-ejabberd_c2s listeners,
-or also globally for ejabberd_s2s_out.
-If the option is not specified for ejabberd_service or
-ejabberd_c2s listeners,
-the globally configured value is used.
-The allowed values are integers and ’undefined’.
-Default value: ’undefined’.
-
- {max_stanza_size, Size}
-
-This option specifies an
-approximate maximum size in bytes of XML stanzas. Approximate,
-because it is calculated with the precision of one block of read
-data. For example
{max_stanza_size, 65536}. The default
-value is infinity. Recommended values are 65536 for c2s
-connections and 131072 for s2s connections. s2s max stanza size
-must always much higher than c2s limit. Change this value with
-extreme care as it can cause unwanted disconnect if set too low.
- - {request_handlers, [ {Path, Module}, ...]}
- To define one or several handlers that will serve HTTP requests.
-The Path is a list of strings; so the URIs that start with that Path will be served by Module.
-For example, if you want mod_foo to serve the URIs that start with /a/b/,
-and you also want mod_http_bind to serve the URIs /http-bind/,
-use this option: {request_handlers, [{["a", "b"], mod_foo}, {["http-bind"], mod_http_bind}]}
-
- {service_check_from, true|false}
-
-
-This option can be used with ejabberd_service only.
-XEP-0114 requires that the domain must match the hostname of the component.
-If this option is set to false, ejabberd will allow the component
-to send stanzas with any arbitrary domain in the ’from’ attribute.
-Only use this option if you are completely sure about it.
-The default value is true, to be compliant with XEP-0114.
-
- {shaper, none|ShaperName}
- This option defines a
-shaper for the port (see section 3.1.6). The default value
-is none.
-
- starttls
- This option
-specifies that STARTTLS encryption is available on connections to the port.
-You should also set the certfile option.
-You can define a certificate file for a specific domain using the global option domain_certfile.
-
- starttls_required
- This option
-specifies that STARTTLS encryption is required on connections to the port.
-No unencrypted connections will be allowed.
-You should also set the certfile option.
-You can define a certificate file for a specific domain using the global option domain_certfile.
-
- tls
- This option specifies that traffic on
-the port will be encrypted using SSL immediately after connecting.
-This was the traditional encryption method in the early Jabber software,
-commonly on port 5223 for client-to-server communications.
-But this method is nowadays deprecated and not recommended.
-The preferable encryption method is STARTTLS on port 5222, as defined
-RFC 3920: XMPP Core,
-which can be enabled in ejabberd with the option starttls.
-If this option is set, you should also set the certfile option.
-The option tls can also be used in ejabberd_http to support HTTPS.
-
- web_admin
- This option
-enables the Web Admin for ejabberd administration which is available
-at
http://server:port/admin/. Login and password are the username and
-password of one of the registered users who are granted access by the
-‘configure’ access rule.
- - zlib
- This
-option specifies that Zlib stream compression (as defined in XEP-0138)
-is available on connections to the port.
-
There are some additional global options that can be specified in the ejabberd configuration file (outside listen):
-
-
-{s2s_use_starttls, true|false}
-
-This option defines whether to
-use STARTTLS for s2s connections.
-
- {s2s_certfile, Path}
- Full path to a
-file containing a SSL certificate.
-
- {domain_certfile, Domain, Path}
-
-Full path to the file containing the SSL certificate for a specific domain.
-
- {outgoing_s2s_options, Methods, Timeout}
-
-Specify which address families to try, in what order, and connect timeout in milliseconds.
-By default it first tries connecting with IPv4, if that fails it tries using IPv6,
-with a timeout of 10000 milliseconds.
-
- {outgoing_s2s_local_address, IPaddress}
-
-Specify which local IP address is desired for the outgoing S2S connections.
-This option is used only if the local and remote addresses
-are of the same IP version (either 4 or 6).
-If this option is not defined, and the ejabberd_s2s_in
-listener address is defined, then that one is used.
-
- {s2s_dns_options, [ {Property, Value}, ...]}
-
-Define properties to use for DNS resolving.
-Allowed Properties are: timeout in seconds which default value is 10
-and retries which default value is 2.
-
- {s2s_default_policy, allow|deny}
-
-The default policy for incoming and outgoing s2s connections to other XMPP servers.
-The default value is allow.
-
- {{s2s_host, Host}, allow|deny}
-
-Defines if incoming and outgoing s2s connections with a specific remote host are allowed or denied.
-This allows to restrict ejabberd to only establish s2s connections
-with a small list of trusted servers, or to block some specific servers.
-
- {s2s_max_retry_delay, Seconds}
-
-The maximum allowed delay for retry to connect after a failed connection attempt.
-Specified in seconds. The default value is 300 seconds (5 minutes).
-
- {max_fsm_queue, Size}
-
-This option specifies the maximum number of elements in the queue of the FSM
-(Finite State Machine).
-Roughly speaking, each message in such queues represents one XML
-stanza queued to be sent into its relevant outgoing stream. If queue size
-reaches the limit (because, for example, the receiver of stanzas is too slow),
-the FSM and the corresponding connection (if any) will be terminated
-and error message will be logged.
-The reasonable value for this option depends on your hardware configuration.
-However, there is no much sense to set the size above 1000 elements.
-This option can be specified for ejabberd_service and
-ejabberd_c2s listeners,
-or also globally for ejabberd_s2s_out.
-If the option is not specified for ejabberd_service or
-ejabberd_c2s listeners,
-the globally configured value is used.
-The allowed values are integers and ’undefined’.
-Default value: ’undefined’.
-
- {route_subdomains, local|s2s}
-
-Defines if ejabberd must route stanzas directed to subdomains locally (compliant with
-RFC 3920: XMPP Core),
-or to foreign server using S2S (compliant with
-RFC 3920 bis).
-
-
For example, the following simple configuration defines:
-
-
-There are three domains. The default certificate file is server.pem.
-However, the c2s and s2s connections to the domain example.com use the file example_com.pem.
-
- Port 5222 listens for c2s connections with STARTTLS,
-and also allows plain connections for old clients.
-
- Port 5223 listens for c2s connections with the old SSL.
-
- Port 5269 listens for s2s connections with STARTTLS. The socket is set for IPv6 instead of IPv4.
-
- Port 3478 listens for STUN requests over UDP.
-
- Port 5280 listens for HTTP requests, and serves the HTTP Poll service.
-
- Port 5281 listens for HTTP requests, and serves the Web Admin using HTTPS as explained in
-section 4.3. The socket only listens connections to the IP address 127.0.0.1.
-
{hosts, ["example.com", "example.org", "example.net"]}.
-{listen,
- [
- {5222, ejabberd_c2s, [
- {access, c2s},
- {shaper, c2s_shaper},
- starttls, {certfile, "/etc/ejabberd/server.pem"},
- {max_stanza_size, 65536}
- ]},
- {5223, ejabberd_c2s, [
- {access, c2s},
- {shaper, c2s_shaper},
- tls, {certfile, "/etc/ejabberd/server.pem"},
- {max_stanza_size, 65536}
- ]},
- {{5269, "::"}, ejabberd_s2s_in, [
- {shaper, s2s_shaper},
- {max_stanza_size, 131072}
- ]},
- {{3478, udp}, ejabberd_stun, []},
- {5280, ejabberd_http, [
- http_poll
- ]},
- {{5281, "127.0.0.1"}, ejabberd_http, [
- web_admin,
- tls, {certfile, "/etc/ejabberd/server.pem"},
- ]}
- ]
-}.
-{s2s_use_starttls, true}.
-{s2s_certfile, "/etc/ejabberd/server.pem"}.
-{domain_certfile, "example.com", "/etc/ejabberd/example_com.pem"}.
-In this example, the following configuration defines that:
-
-
-c2s connections are listened for on port 5222 (all IPv4 addresses) and
-on port 5223 (SSL, IP 192.168.0.1 and fdca:8ab6:a243:75ef::1) and denied
-for the user called ‘bad’.
-
- s2s connections are listened for on port 5269 (all IPv4 addresses)
-with STARTTLS for secured traffic enabled.
-Incoming and outgoing connections of remote XMPP servers are denied,
-only two servers can connect: "jabber.example.org" and "example.com".
-
- Port 5280 is serving the Web Admin and the HTTP Polling service
-in all the IPv4 addresses. Note
-that it is also possible to serve them on different ports. The second
-example in section 4.3 shows how exactly this can be done.
-
- All users except for the administrators have a traffic of limit
-1,000 Bytes/second
-
- The
-AIM transport
-aim.example.org is connected to port 5233 on localhost IP addresses
-(127.0.0.1 and ::1) with password ‘aimsecret’.
-
- The ICQ transport JIT (icq.example.org and
-sms.example.org) is connected to port 5234 with password
-‘jitsecret’.
-
- The
-MSN transport
-msn.example.org is connected to port 5235 with password
-‘msnsecret’.
-
- The
-Yahoo! transport
-yahoo.example.org is connected to port 5236 with password
-‘yahoosecret’.
-
- The Gadu-Gadu transport gg.example.org is
-connected to port 5237 with password ‘ggsecret’.
-
- The
-Jabber Mail Component
-jmc.example.org is connected to port 5238 with password
-‘jmcsecret’.
-
- The service custom has enabled the special option to avoiding checking the from attribute in the packets send by this component. The component can send packets in behalf of any users from the server, or even on behalf of any server.
-
{acl, blocked, {user, "bad"}}.
-{access, c2s, [{deny, blocked},
- {allow, all}]}.
-{shaper, normal, {maxrate, 1000}}.
-{access, c2s_shaper, [{none, admin},
- {normal, all}]}.
-{listen,
- [{5222, ejabberd_c2s, [
- {access, c2s},
- {shaper, c2s_shaper}
- ]},
- {{5223, {192, 168, 0, 1}}, ejabberd_c2s, [
- {access, c2s},
- ssl, {certfile, "/path/to/ssl.pem"}
- ]},
- {{5223, {16#fdca, 16#8ab6, 16#a243, 16#75ef, 0, 0, 0, 1}},
- ejabberd_c2s, [
- {access, c2s},
- ssl, {certfile, "/path/to/ssl.pem"}
- ]},
- {5269, ejabberd_s2s_in, []},
- {{5280, {0, 0, 0, 0}}, ejabberd_http, [
- http_poll,
- web_admin
- ]},
- {{5233, {127, 0, 0, 1}}, ejabberd_service, [
- {hosts, ["aim.example.org"],
- [{password, "aimsecret"}]}
- ]},
- {{5233, "::1"}, ejabberd_service, [
- {hosts, ["aim.example.org"],
- [{password, "aimsecret"}]}
- ]},
- {5234, ejabberd_service, [{hosts, ["icq.example.org", "sms.example.org"],
- [{password, "jitsecret"}]}]},
- {5235, ejabberd_service, [{hosts, ["msn.example.org"],
- [{password, "msnsecret"}]}]},
- {5236, ejabberd_service, [{hosts, ["yahoo.example.org"],
- [{password, "yahoosecret"}]}]},
- {5237, ejabberd_service, [{hosts, ["gg.example.org"],
- [{password, "ggsecret"}]}]},
- {5238, ejabberd_service, [{hosts, ["jmc.example.org"],
- [{password, "jmcsecret"}]}]},
- {5239, ejabberd_service, [{hosts, ["custom.example.org"],
- [{password, "customsecret"}]},
- {service_check_from, false}]}
- ]
-}.
-{s2s_use_starttls, true}.
-{s2s_certfile, "/path/to/ssl.pem"}.
-{s2s_default_policy, deny}.
-{{s2s_host,"jabber.example.org"}, allow}.
-{{s2s_host,"example.com"}, allow}.
-Note, that for services based in jabberd14 or WPJabber
-you have to make the transports log and do XDB by themselves:
-
<!--
- You have to add elogger and rlogger entries here when using ejabberd.
- In this case the transport will do the logging.
- -->
-
- <log id='logger'>
- <host/>
- <logtype/>
- <format>%d: [%t] (%h): %s</format>
- <file>/var/log/jabber/service.log</file>
- </log>
-
- <!--
- Some XMPP server implementations do not provide
- XDB services (for example, jabberd2 and ejabberd).
- xdb_file.so is loaded in to handle all XDB requests.
- -->
-
- <xdb id="xdb">
- <host/>
- <load>
- <!-- this is a lib of wpjabber or jabberd14 -->
- <xdb_file>/usr/lib/jabber/xdb_file.so</xdb_file>
- </load>
- <xdb_file xmlns="jabber:config:xdb_file">
- <spool><jabberd:cmdline flag='s'>/var/spool/jabber</jabberd:cmdline></spool>
- </xdb_file>
- </xdb>
-
-
-
The option auth_method defines the authentication methods that are used
-for user authentication.
-Usually only one method is defined, with this syntax:
-
- {auth_method, Method}.
-This full syntax can be used to specify one or more methods:
-
- {auth_method, [Method1, Method2, ...]}.
The following authentication methods are supported by ejabberd:
-
-
-database storage in internal Mnesia or ODBC — See section 3.1.4.
-
- external — See section 3.1.4.
-
- ldap — See section 3.2.5.
-
- anonymous — See section 3.1.4.
-
- pam — See section 3.1.4.
-
- a method with SASL GSSAPI — See section 3.1.4.
-
Account creation is only supported by the methods:
-internal Mnesia storage, ODBC storage, and external.
-
-
You can configure ejabberd to use the database storage authentication method,
-and store either in the internal Mnesia database or in an ODBC database.
-The specific storage is configured with the option:
-
{auth_storage, mnesia|odbc}
-When the storage is configured for ODBC, the ODBC server is
-configured with the odbc_server option, see
-3.2.1 for MySQL, 3.2.3 for PostgreSQL, 3.2.2 for MSSQL, and 3.2.4 for generic ODBC.
Examples:
-
-
-To use internal Mnesia storage on all virtual hosts:
-
{auth_method, storage}.
-{auth_storage, mnesia}.
- - To use ODBC storage on all virtual hosts:
-
{auth_method, storage}.
-{auth_storage, odbc}.
- - To use Mnesia storage on example.org,
-ODBC storage in a MySQL database on example.com,
-ODBC storage in a PostgreSQL database on example2.com,
-and LDAP on example.net:
-
{host_config, "example.org", [
- {auth_method, storage},
- {auth_storage, mnesia}
-]}.
-{host_config, "example.com", [
- {auth_method, storage},
- {auth_storage, odbc},
- {odbc_server, {mysql, "localhost", "test", "root", "password"}}
-]}.
-{host_config, "example2.com", [
- {auth_method, storage},
- {auth_storage, odbc},
- {odbc_server, "DSN=database;UID=ejabberd;PWD=password"}
-]}.
-{host_config, "example.net", [
- {auth_method, ldap}
-]}.
-
-
-
In this authentication method, when ejabberd starts,
-it start a script, and calls it to perform authentication tasks.
The server administrator can write the external authentication script
-in any language.
-The details on the interface between ejabberd and the script are described
-in the ejabberd Developers Guide.
-There are also several example authentication scripts.
These are the specific options:
-
-
-{extauth_program, PathToScript}
-
-Indicate in this option the full path to the external authentication script.
-The script must be executable by ejabberd.
- {extauth_instances, Integer}
-
-Indicate how many instances of the script to run simultaneously to serve authentication in the virtual host.
-The default value is the minimum number: 1.
- {extauth_cache, false|CacheTimeInteger}
-
-The value false disables the caching feature, this is the default.
-The integer 0 (zero) enables caching for statistics, but doesn’t use that cached information to authenticate users.
-If another integer value is set, caching is enabled both for statistics and for authentication:
-the CacheTimeInteger indicates the number of seconds that ejabberd can reuse
-the authentication information since the user last disconnected,
-to verify again the user authentication without querying again the extauth script.
-Note: caching should not be enabled in a host if internal auth is also enabled.
-If caching is enabled, mod_last must be enabled also in that vhost.
-
This example sets external authentication, the extauth script, enables caching for 10 minutes,
-and starts three instances of the script for each virtual host defined in ejabberd:
-
{auth_method, external}.
-{extauth_program, "/etc/ejabberd/JabberAuth.class.php"}.
-{extauth_cache, 600}.
-{extauth_instances, 3}.
-
-
-
The value anonymous will enable the internal authentication method.
The anonymous authentication method can be configured with the following
-options. Remember that you can use the host_config option to set virtual
-host specific options (see section 3.1.2). Note that there also
-is a detailed tutorial regarding SASL
-Anonymous and anonymous login configuration.
-
-{allow_multiple_connections, false|true}
- This option is only used
-when the anonymous mode is
-enabled. Setting it to true means that the same username can be taken
-multiple times in anonymous login mode if different resource are used to
-connect. This option is only useful in very special occasions. The default
-value is false.
-
- {anonymous_protocol, sasl_anon | login_anon | both}
-
-sasl_anon means
-that the SASL Anonymous method will be used. login_anon means that the
-anonymous login method will be used. both means that SASL Anonymous and
-login anonymous are both enabled.
-
Those options are defined for each virtual host with the host_config
-parameter (see section 3.1.2).
Examples:
-
-
-To enable anonymous login on all virtual hosts:
-
{auth_method, anonymous}.
-{anonymous_protocol, login_anon}.
- - Similar as previous example, but limited to public.example.org:
-
{host_config, "public.example.org", [{auth_method, anonymous},
- {anonymous_protocol, login_anon}]}.
- - To enable anonymous login and internal authentication on a virtual host:
-
{host_config, "public.example.org", [{auth_method, [internal, anonymous]},
- {anonymous_protocol, login_anon}]}.
- - To enable SASL Anonymous on a virtual host:
-
{host_config, "public.example.org", [{auth_method, anonymous},
- {anonymous_protocol, sasl_anon}]}.
- - To enable SASL Anonymous and anonymous login on a virtual host:
-
{host_config, "public.example.org", [{auth_method, anonymous},
- {anonymous_protocol, both}]}.
- - To enable SASL Anonymous, anonymous login, and internal authentication on
-a virtual host:
-
{host_config, "public.example.org", [{auth_method, [internal, anonymous]},
- {anonymous_protocol, both}]}.
-
-
-
ejabberd supports authentication via Pluggable Authentication Modules (PAM).
-PAM is currently supported in AIX, FreeBSD, HP-UX, Linux, Mac OS X, NetBSD and Solaris.
-PAM authentication is disabled by default, so you have to configure and compile
-ejabberd with PAM support enabled:
-
./configure --enable-pam && make install
-
Options:
-
-
-{pam_service, Name}
- This option defines the PAM service name.
-Default is "ejabberd". Refer to the PAM documentation of your operation system
-for more information.
-
- {pam_userinfotype, username|jid}
-
-This option defines what type of information about the user ejabberd
-provides to the PAM service: only the username, or the user JID.
-Default is username.
-
Example:
-
{auth_method, pam}.
-{pam_service, "ejabberd"}.
-Though it is quite easy to set up PAM support in ejabberd, PAM itself introduces some
-security issues:
-
-
ejabberd supports SASL GSSAPI authentication.
-It is compatible with SSO as implemented in Spark 2.5.3.
To use this feature, you have to download the esasl library
-source code from
-http://github.com/mikma/esasl,
-compile and install it. Example instructions:
-
git clone git://github.com/mikma/esasl.git
-cd esasl
-./configure --prefix=/usr
-make
-sudo make install
-
After doing this, check that esasl was installed in the /usr/lib/erlang/lib/ directory.
-For compiling esasl, maybe you need to get some development files;
-(for example, in Debian, the package libgsasl7-dev).
The SASL GSSAPI mechanism uses a authentication backend only to check for a
-valid user name when authorizing the user.
-The authentication is done by esasl against a Kerberos key server (KDC).
-Often Kerberos authentication is combined with LDAP to store user account information.
-To do that, edit ejabberd.cfg and modify the auth_mehtod depending
-on what you want to allow. For example:
-
{auth_method, [ldap]}.
-Now define the Kerberos realm:
-
{sasl_realm, "Kerberos realm"}.
-and manually set the FQDN.
-ejabberd does a reverse lookup on the connecting IP and uses
-that FQDN for locating its keytab entry in the keytab file.
-
{sasl_fqdn, "dbs.example.com"}.
-The environment variable KRB5_KTNAME is the location of the keytab file,
-and needs to be set before starting ejabberd.
-The keytab referenced by KRB5_KTNAME should contain the principal xmpp/FQDN,
-where FQDN is the fully qualified host name of the ejabberd server.
-For example, in Debian, add to the file /etc/ejabberd/default the line:
-
export KRB5_KTNAME="/etc/keytabs/xmpp-dbs.example.com-EXAMPLE.COM.keytab"
-
-
-
-
-
Access control in ejabberd is performed via Access Control Lists (ACLs). The
-declarations of ACLs in the configuration file have the following syntax:
-
- {acl, ACLName, ACLValue}.
ACLValue can be one of the following:
-
-
-all
- Matches all JIDs. Example:
-
{acl, all, all}.
- - {user, Username}
- Matches the user with the name
-Username at the first virtual host. Example:
-
{acl, admin, {user, "yozhik"}}.
- - {user, Username, Server}
- Matches the user with the JID
-Username@Server and any resource. Example:
-
{acl, admin, {user, "yozhik", "example.org"}}.
- - {server, Server}
- Matches any JID from server
-Server. Example:
-
{acl, exampleorg, {server, "example.org"}}.
- - {resource, Resource}
- Matches any JID with a resource
-Resource. Example:
-
{acl, mucklres, {resource, "muckl"}}.
- - {shared_group, Groupname}
- Matches any member of a Shared Roster Group with name Groupname in the virtual host. Example:
-
{acl, techgroupmembers, {shared_group, "techteam"}}.
- - {shared_group, Groupname, Server}
- Matches any member of a Shared Roster Group with name Groupname in the virtual host Server. Example:
-
{acl, techgroupmembers, {shared_group, "techteam", "example.org"}}.
- - {user_regexp, Regexp}
- Matches any local user with a name that
-matches Regexp on local virtual hosts. Example:
-
{acl, tests, {user_regexp, "^test[0-9]*$"}}.
- - {user_regexp, UserRegexp, Server}
- Matches any user with a name
-that matches Regexp at server Server. Example:
-
{acl, tests, {user_Userregexp, "^test", "example.org"}}.
- - {server_regexp, Regexp}
- Matches any JID from the server that
-matches Regexp. Example:
-
{acl, icq, {server_regexp, "^icq\\."}}.
- - {resource_regexp, Regexp}
- Matches any JID with a resource that
-matches Regexp. Example:
-
{acl, icq, {resource_regexp, "^laptop\\."}}.
- - {node_regexp, UserRegexp, ServerRegexp}
- Matches any user
-with a name that matches UserRegexp at any server that matches
-ServerRegexp. Example:
-
{acl, yohzik, {node_regexp, "^yohzik$", "^example.(com|org)$"}}.
- - {user_glob, Glob}
-
-
- {user_glob, Glob, Server}
-
-
- {server_glob, Glob}
-
-
- {resource_glob, Glob}
-
-
- {node_glob, UserGlob, ServerGlob}
- This is the same as
-above. However, it uses shell glob patterns instead of regexp. These patterns
-can have the following special characters:
-
-
-*
- matches any string including the null string.
-
- ?
- matches any single character.
-
- [...]
- matches any of the enclosed characters. Character
-ranges are specified by a pair of characters separated by a ‘-’.
-If the first character after ‘[’ is a ‘!’, any
-character not enclosed is matched.
-
-
The following ACLName are pre-defined:
-
-
-all
- Matches any JID.
-
- none
- Matches no JID.
-
-
-
An entry allowing or denying access to different services.
-The syntax is:
-
- {access, AccessName, [ {allow|deny, ACLName}, ...]}.
When a JID is checked to have access to Accessname, the server
-sequentially checks if that JID matches any of the ACLs that are named in the
-second elements of the tuples in the list. If it matches, the first element of
-the first matched tuple is returned, otherwise the value ‘deny’ is
-returned.
If you define specific Access rights in a virtual host,
-remember that the globally defined Access rights have precedence over those.
-This means that, in case of conflict, the Access granted or denied in the global server is used
-and the Access of a virtual host doesn’t have effect.
Example:
-
{access, configure, [{allow, admin}]}.
-{access, something, [{deny, badmans},
- {allow, all}]}.
-The following AccessName are pre-defined:
-
-
-all
- Always returns the value ‘allow’.
-
- none
- Always returns the value ‘deny’.
-
-
-
The special access max_user_sessions specifies the maximum
-number of sessions (authenticated connections) per user. If a user
-tries to open more sessions by using different resources, the first
-opened session will be disconnected. The error session replaced
-will be sent to the disconnected session. The value for this option
-can be either a number, or infinity. The default value is
-infinity.
The syntax is:
-
- {access, max_user_sessions, [ {MaxNumber, ACLName}, ...]}.
This example limits the number of sessions per user to 5 for all users, and to 10 for admins:
-
{access, max_user_sessions, [{10, admin}, {5, all}]}.
-
-
-
The special access max_s2s_connections specifies how many
-simultaneous S2S connections can be established to a specific remote XMPP server.
-The default value is 1.
-There’s also available the access max_s2s_connections_per_node.
The syntax is:
-
- {access, max_s2s_connections, [ {MaxNumber, ACLName}, ...]}.
Examples:
-
-
-
Shapers enable you to limit connection traffic.
-The syntax is:
-
- {shaper, ShaperName, Kind}.
-Currently only one kind of shaper called maxrate is available. It has the
-following syntax:
-
- {maxrate, Rate}
-where Rate stands for the maximum allowed incoming rate in bytes per
-second.
-When a connection exceeds this limit, ejabberd stops reading from the socket
-until the average rate is again below the allowed maximum.
Examples:
-
-
-To define a shaper named ‘normal’ with traffic speed limited to
-1,000 bytes/second:
-
{shaper, normal, {maxrate, 1000}}.
- - To define a shaper named ‘fast’ with traffic speed limited to
-50,000 bytes/second:
-
{shaper, fast, {maxrate, 50000}}.
-
-
-
The option language defines the default language of server strings that
-can be seen by XMPP clients. If a XMPP client does not support
-xml:lang, the specified language is used.
The option syntax is:
-
- {language, Language}.
The default value is en.
-In order to take effect there must be a translation file
-Language.msg in ejabberd’s msgs directory.
For example, to set Russian as default language:
-
{language, "ru"}.
-Appendix A provides more details about internationalization and localization.
-
-
Some ejabberd modules can be configured to require a CAPTCHA challenge on certain actions.
-If the client does not support CAPTCHA Forms (XEP-0158),
-a web link is provided so the user can fill the challenge in a web browser.
An example script is provided that generates the image
-using ImageMagick’s Convert program.
The configurable options are:
-
-
-{captcha_cmd, Path}
-
-Full path to a script that generates the image.
-The default value is an empty string: ""
-
- {captcha_host, Host}
-
-Host part of the URL sent to the user.
-You can include the port number.
-The URL sent to the user is formed by: http://Host/captcha/
-The default value is the first hostname configured.
-
Additionally, an ejabberd_http listener must be enabled with the captcha option.
-See section 3.1.3.
Example configuration:
-
{hosts, ["example.org"]}.
-
-{captcha_cmd, "/lib/ejabberd/priv/bin/captcha.sh"}.
-{captcha_host, "example.org:5280"}.
-
-{listen,
- [
- ...
- {5280, ejabberd_http, [
- captcha,
- ...
- ]
- }
-
-]}.
-
-
-
ejabberd is able to act as a stand-alone STUN server
-(RFC 5389). Currently only Binding usage
-is supported. In that role ejabberd helps clients with Jingle ICE (XEP-0176) support to discover their external addresses and ports.
You should configure ejabberd_stun listening module as described in 3.1.3 section.
-If certfile option is defined, ejabberd multiplexes TCP and
-TLS over TCP connections on the same port. Obviously, certfile option
-is defined for tcp only. Note however that TCP or TLS over TCP
-support is not required for Binding usage and is reserved for
-TURN
-functionality. Feel free to configure udp transport only.
Example configuration:
-
{listen,
- [
- ...
- {{3478, udp}, ejabberd_stun, []},
- {3478, ejabberd_stun, []},
- {5349, ejabberd_stun, [{certfile, "/etc/ejabberd/server.pem"}]},
- ...
- ]
-}.
-You also need to configure DNS SRV records properly so clients can easily discover a
-STUN server serving your XMPP domain. Refer to section
-DNS Discovery of a Server
-of RFC 5389 for details.
Example DNS SRV configuration:
-
_stun._udp IN SRV 0 0 3478 stun.example.com.
-_stun._tcp IN SRV 0 0 3478 stun.example.com.
-_stuns._tcp IN SRV 0 0 5349 stun.example.com.
-
-
-
The option include_config_file in a configuration file instructs ejabberd to include other configuration files immediately.
The basic syntax is:
-
- {include_config_file, Filename}.
-It is possible to specify suboptions using the full syntax:
-
- {include_config_file, Filename, [Suboption, ...]}.
The filename can be indicated either as an absolute path,
-or relative to the main ejabberd configuration file.
-It isn’t possible to use wildcards.
-The file must exist and be readable.
The allowed suboptions are:
-
-
-{disallow, [Optionname, ...]}
- Disallows the usage of those options in the included configuration file.
-The options that match this criteria are not accepted.
-The default value is an empty list: []
-
- {allow_only, [Optionname, ...]}
- Allows only the usage of those options in the included configuration file.
-The options that do not match this criteria are not accepted.
-The default value is: all
-
This is a basic example:
-
{include_config_file, "/etc/ejabberd/additional.cfg"}.
-In this example, the included file is not allowed to contain a listen option.
-If such an option is present, the option will not be accepted.
-The file is in a subdirectory from where the main configuration file is.
-
{include_config_file, "./example.org/additional_not_listen.cfg", [{disallow, [listen]}]}.
-In this example, ejabberd.cfg defines some ACL and Access rules,
-and later includes another file with additional rules:
-
{acl, admin, {user, "admin", "localhost"}}.
-{access, announce, [{allow, admin}]}.
-{include_config_file, "/etc/ejabberd/acl_and_access.cfg", [{allow_only, [acl, access]}]}.
-and content of the file acl_and_access.cfg can be, for example:
-
{acl, admin, {user, "bob", "localhost"}}.
-{acl, admin, {user, "jan", "localhost"}}.
-
-
-
In the ejabberd configuration file,
-it is possible to define a macro for a value
-and later use this macro when defining an option.
A macro is defined with this syntax:
-
- {define_macro, ’MACRO’, Value}.
-The MACRO must be surrounded by single quotation marks,
-and all letters in uppercase; check the examples bellow.
-The value can be any valid arbitrary Erlang term.
The first definition of a macro is preserved,
-and additional definitions of the same macro are forgotten.
Macros are processed after
-additional configuration files have been included,
-so it is possible to use macros that
-are defined in configuration files included before the usage.
It isn’t possible to use a macro in the definition
-of another macro.
There are two ways to use a macro:
-
- ’MACRO’
-
-You can put this instead of a value in an ejabberd option,
-and will be replaced with the value previously defined.
-If the macro is not defined previously,
-the program will crash and report an error.
- {use_macro, ’MACRO’, Defaultvalue}
-
-Use a macro even if it may not be defined.
-If the macro is not defined previously,
-the provided defaultvalue is used.
-This usage behaves as if it were defined and used this way:
-
{define_macro, 'MACRO', Defaultvalue}.
-'MACRO'
-
This example shows the basic usage of a macro:
-
{define_macro, 'LOG_LEVEL_NUMBER', 5}.
-{loglevel, 'LOG_LEVEL_NUMBER'}.
-The resulting option interpreted by ejabberd is: {loglevel, 5}.
This example shows that values can be any arbitrary Erlang term:
-
{define_macro, 'USERBOB', {user, "bob", "localhost"}}.
-{acl, admin, 'USERBOB'}.
-The resulting option interpreted by ejabberd is: {acl, admin, {user, "bob", "localhost"}}.
This complex example:
-
{define_macro, 'NUMBER_PORT_C2S', 5222}.
-{define_macro, 'PORT_S2S_IN', {5269, ejabberd_s2s_in, []}}.
-{listen,
- [
- {'NUMBER_PORT_C2S', ejabberd_c2s, []},
- 'PORT_S2S_IN',
- {{use_macro, 'NUMBER_PORT_HTTP', 5280}, ejabberd_http, []}
- ]
-}.
-produces this result after being interpreted:
-
{listen,
- [
- {5222, ejabberd_c2s, []},
- {5269, ejabberd_s2s_in, []},
- {5280, ejabberd_http, []}
- ]
-}.
-
-
-
-
ejabberd uses its internal Mnesia database by default. However, it is
-possible to use a relational database or an LDAP server to store persistent,
-long-living data. ejabberd is very flexible: you can configure different
-authentication methods for different virtual hosts, you can configure different
-authentication mechanisms for the same virtual host (fallback), you can set
-different storage systems for modules, and so forth.
The following databases are supported by ejabberd:
-
The following LDAP servers are tested with ejabberd:
-
-
-Active Directory
-(see section 3.2.5)
-
- OpenLDAP
-
- Normally any LDAP compatible server should work; inform us about your
-success with a not-listed server so that we can list it here.
-
Important note about virtual hosting:
-if you define several domains in ejabberd.cfg (see section 3.1.1),
-you probably want that each virtual host uses a different configuration of database, authentication and storage,
-so that usernames do not conflict and mix between different virtual hosts.
-For that purpose, the options described in the next sections
-must be set inside a host_config for each vhost (see section 3.1.2).
-For example:
-
{host_config, "public.example.org", [
- {odbc_server, {pgsql, "localhost", "database-public-example-org", "ejabberd", "password"}},
- {auth_method, storage},
- {auth_storage, odbc}
-]}.
-
-
-
Although this section will describe ejabberd’s configuration when you want to
-use the native MySQL driver, it does not describe MySQL’s installation and
-database creation. Check the MySQL documentation and the tutorial Using ejabberd with MySQL native driver for information regarding these topics.
-Note that the tutorial contains information about ejabberd’s configuration
-which is duplicate to this section.
Moreover, the file mysql.sql in the directory src/odbc might be interesting for
-you. This file contains the ejabberd schema for MySQL. At the end of the file
-you can find information to update your database schema.
-
-
You can skip this step if you installed ejabberd using a binary installer or
-if the binary packages of ejabberd you are using include support for MySQL.
-
-First, install the Erlang
-MySQL library. Make sure the compiled files are in your Erlang path; you can
-put them for example in the same directory as your ejabberd .beam files.
-
- Then, configure and install ejabberd with ODBC support enabled (this is
-also needed for native MySQL support!). This can be done, by using next
-commands:
-
./configure --enable-odbc && make install
-
-
-
The actual database access is defined in the option odbc_server. Its
-value is used to define if we want to use ODBC, or one of the two native
-interface available, PostgreSQL or MySQL.
To use the native MySQL interface, you can pass a tuple of the following form as
-parameter:
-
- {mysql, "Server", "Database", "Username", "Password"}
mysql is a keyword that should be kept as is. For example:
-
- {odbc_server, {mysql, "localhost", "test", "root", "password"}}.
Optionally, it is possible to define the MySQL port to use. This
-option is only useful, in very rare cases, when you are not running
-MySQL with the default port setting. The mysql parameter
-can thus take the following form:
-
- {mysql, "Server", Port, "Database", "Username", "Password"}
The Port value should be an integer, without quotes. For example:
-
- {odbc_server, {mysql, "localhost", Port, "test", "root", "password"}}.
By default ejabberd opens 10 connections to the database for each virtual host.
-Use this option to modify the value:
-
{odbc_pool_size, 10}.
-You can configure an interval to make a dummy SQL request
-to keep alive the connections to the database.
-The default value is ’undefined’, so no keepalive requests are made.
-Specify in seconds: for example 28800 means 8 hours.
-
{odbc_keepalive_interval, undefined}.
-If the connection to the database fails, ejabberd waits 30 seconds before retrying.
-You can modify this interval with this option:
-
{odbc_start_interval, 30}.
-
-
-
See section 3.1.4.
-
-
MySQL also can be used to store information into from several ejabberd
-modules.
-See section 3.3.1 to see which modules support an ODBC storage backend.
-To configure the module to use ODBC as storage backend, add the option
-{backend, odbc} to the module.
-
-
Although this section will describe ejabberd’s configuration when you want to
-use Microsoft SQL Server, it does not describe Microsoft SQL Server’s
-installation and database creation. Check the MySQL documentation and the
-tutorial Using ejabberd with MySQL native driver for information regarding these topics.
-Note that the tutorial contains information about ejabberd’s configuration
-which is duplicate to this section.
Moreover, the file mssql.sql in the directory src/odbc might be interesting for
-you. This file contains the ejabberd schema for Microsoft SQL Server. At the end
-of the file you can find information to update your database schema.
-
-
You can skip this step if you installed ejabberd using a binary installer or
-if the binary packages of ejabberd you are using include support for ODBC.
If you want to use Microsoft SQL Server with ODBC, you need to configure,
-compile and install ejabberd with support for ODBC and Microsoft SQL Server
-enabled. This can be done, by using next commands:
-
./configure --enable-odbc --enable-mssql && make install
-
-
-
See section 3.1.4.
-
-
The configuration of Authentication for a Microsoft SQL Server
-is the same as the configuration for
-ODBC compatible servers (see section 3.2.4).
-
-
Microsoft SQL Server also can be used to store information into from several
-ejabberd modules.
-See section 3.3.1 to see which modules support an ODBC storage backend.
-To configure the module to use ODBC as storage backend, add the option
-{backend, odbc} to the module.
-
-
Although this section will describe ejabberd’s configuration when you want to
-use the native PostgreSQL driver, it does not describe PostgreSQL’s installation
-and database creation. Check the PostgreSQL documentation and the tutorial Using ejabberd with MySQL native driver for information regarding these topics.
-Note that the tutorial contains information about ejabberd’s configuration
-which is duplicate to this section.
Also the file pg.sql in the directory src/odbc might be interesting for you.
-This file contains the ejabberd schema for PostgreSQL. At the end of the file
-you can find information to update your database schema.
-
-
You can skip this step if you installed ejabberd using a binary installer or
-if the binary packages of ejabberd you are using include support for
-PostgreSQL.
-
-First, install the Erlang pgsql library from
-ejabberd-modules SVN repository.
-Make sure the compiled
-files are in your Erlang path; you can put them for example in the same
-directory as your ejabberd .beam files.
-
- Then, configure, compile and install ejabberd with ODBC support enabled
-(this is also needed for native PostgreSQL support!). This can be done, by
-using next commands:
-
./configure --enable-odbc && make install
-
-
-
The actual database access is defined in the option odbc_server. Its
-value is used to define if we want to use ODBC, or one of the two native
-interface available, PostgreSQL or MySQL.
To use the native PostgreSQL interface, you can pass a tuple of the following
-form as parameter:
-
- {pgsql, "Server", "Database", "Username", "Password"}
pgsql is a keyword that should be kept as is. For example:
-
- {odbc_server, {pgsql, "localhost", "database", "ejabberd", "password"}}.
Optionally, it is possible to define the PostgreSQL port to use. This
-option is only useful, in very rare cases, when you are not running
-PostgreSQL with the default port setting. The pgsql parameter
-can thus take the following form:
-
- {pgsql, "Server", Port, "Database", "Username", "Password"}
The Port value should be an integer, without quotes. For example:
-
- {odbc_server, {pgsql, "localhost", 5432, "database", "ejabberd", "password"}}.
By default ejabberd opens 10 connections to the database for each virtual host.
-Use this option to modify the value:
-
{odbc_pool_size, 10}.
-You can configure an interval to make a dummy SQL request
-to keep alive the connections to the database.
-The default value is ’undefined’, so no keepalive requests are made.
-Specify in seconds: for example 28800 means 8 hours.
-
{odbc_keepalive_interval, undefined}.
-
-
-
See section 3.1.4.
-
-
PostgreSQL also can be used to store information into from several ejabberd
-modules.
-See section 3.3.1 to see which modules support an ODBC storage backend.
-To configure the module to use ODBC as storage backend, add the option
-{backend, odbc} to the module.
-
-
Although this section will describe ejabberd’s configuration when you want to
-use the ODBC driver, it does not describe the installation and database creation
-of your database. Check the documentation of your database. The tutorial Using ejabberd with MySQL native driver also can help you. Note that the tutorial
-contains information about ejabberd’s configuration which is duplicate to
-this section.
-
You can skip this step if you installed ejabberd using a binary installer or
-if the binary packages of ejabberd you are using include support for
-ODBC.
-
-First, install the Erlang
-MySQL library. Make sure the compiled files are in your Erlang path; you can
-put them for example in the same directory as your ejabberd .beam files.
-
- Then, configure, compile and install ejabberd with ODBC support
-enabled. This can be done, by using next commands:
-
./configure --enable-odbc && make install
-
-
-
The actual database access is defined in the option odbc_server. Its
-value is used to defined if we want to use ODBC, or one of the two native
-interface available, PostgreSQL or MySQL.
To use a relational database through ODBC, you can pass the ODBC connection
-string as odbc_server parameter. For example:
-
{odbc_server, "DSN=database;UID=ejabberd;PWD=password"}.
-By default ejabberd opens 10 connections to the database for each virtual host.
-Use this option to modify the value:
-
{odbc_pool_size, 10}.
-You can configure an interval to make a dummy SQL request
-to keep alive the connections to the database.
-The default value is ’undefined’, so no keepalive requests are made.
-Specify in seconds: for example 28800 means 8 hours.
-
{odbc_keepalive_interval, undefined}.
-
-
-
See section 3.1.4.
-
-
An ODBC compatible database also can be used to store information into from
-several ejabberd modules.
-See section 3.3.1 to see which modules support an ODBC storage backend.
-To configure the module to use ODBC as storage backend, add the option
-{backend, odbc} to the module.
-
-
ejabberd has built-in LDAP support. You can authenticate users against LDAP
-server and use LDAP directory as vCard storage. Shared rosters are not supported
-yet.
Usually ejabberd treats LDAP as a read-only storage:
-it is possible to consult data, but not possible to
-create accounts or edit vCard that is stored in LDAP.
-However, it is possible to change passwords if mod_register module is enabled
-and LDAP server supports
-RFC 3062.
-
Two connections are established to the LDAP server per vhost,
-one for authentication and other for regular calls.
Parameters:
-
-
-{ldap_servers, [Servers, ...]}
- List of IP addresses or DNS names of your
-LDAP servers. This option is required.
-
- {ldap_encrypt, none|tls}
- Type of connection encryption to the LDAP server.
-Allowed values are: none, tls.
-The value tls enables encryption by using LDAP over SSL.
-Note that STARTTLS encryption is not supported.
-The default value is: none.
-
- {ldap_tls_verify, false|soft|hard}
-
-This option specifies whether to verify LDAP server certificate or not when TLS is enabled.
-When hard is enabled ejabberd doesn’t proceed if a certificate is invalid.
-When soft is enabled ejabberd proceeds even if check fails.
-The default is false which means no checks are performed.
-
- {ldap_port, Number}
- Port to connect to your LDAP server.
-The default port is 389 if encryption is disabled; and 636 if encryption is enabled.
-If you configure a value, it is stored in ejabberd’s database.
-Then, if you remove that value from the configuration file,
-the value previously stored in the database will be used instead of the default port.
-
- {ldap_rootdn, RootDN}
- Bind DN. The default value
-is "" which means ‘anonymous connection’.
-
- {ldap_password, Password}
- Bind password. The default
-value is "".
-
Example:
-
{auth_method, ldap}.
-{ldap_servers, ["ldap.example.org"]}.
-{ldap_port, 389}.
-{ldap_rootdn, "cn=Manager,dc=domain,dc=org"}.
-{ldap_password, "secret"}.
-
-
You can authenticate users against an LDAP directory.
-Note that current LDAP implementation does not support SASL authentication.
Available options are:
-
-{ldap_base, Base}
- LDAP base directory which stores
-users accounts. This option is required.
-
- {ldap_uids, [ {ldap_uidattr} | {ldap_uidattr, ldap_uidattr_format}, ...]}
-
-LDAP attribute which holds a list of attributes to use as alternatives for getting the JID.
-The default attributes are [{"uid", "%u"}].
-The attributes are of the form:
-[{ldap_uidattr}] or [{ldap_uidattr, ldap_uidattr_format}].
-You can use as many comma separated attributes as needed.
-The values for ldap_uidattr and
-ldap_uidattr_format are described as follow:
-
-
-ldap_uidattr
- LDAP attribute which holds
-the user’s part of a JID. The default value is "uid".
-
- ldap_uidattr_format
- Format of
-the ldap_uidattr variable. The format must contain one and
-only one pattern variable "%u" which will be replaced by the
-user’s part of a JID. For example, "%u@example.org". The default
-value is "%u".
-
- - {ldap_filter, Filter}
-
-RFC 4515 LDAP filter. The
-default Filter value is: undefined. Example:
-"(&(objectClass=shadowAccount)(memberOf=Jabber Users))". Please, do
-not forget to close brackets and do not use superfluous whitespaces. Also you
-must not use ldap_uidattr attribute in filter because this
-attribute will be substituted in LDAP filter automatically.
-
- {ldap_filter, Filter}
-
-RFC 4515 LDAP filter. The
-default Filter value is: undefined. Example:
-"(&(objectClass=shadowAccount)(memberOf=Jabber Users))". Please, do
-not forget to close brackets and do not use superfluous whitespaces. Also you
-must not use ldap_uidattr attribute in filter because this
-attribute will be substituted in LDAP filter automatically.
-
- {ldap_dn_filter, { Filter, FilterAttrs }}
-
-This filter is applied on the results returned by the main filter. This filter
-performs additional LDAP lookup to make the complete result. This is useful
-when you are unable to define all filter rules in ldap_filter. You
-can define "%u", "%d", "%s" and "%D" pattern
-variables in Filter: "%u" is replaced by a user’s part of a JID,
-"%d" is replaced by the corresponding domain (virtual host),
-all "%s" variables are consecutively replaced by values of FilterAttrs
-attributes and "%D" is replaced by Distinguished Name. By default
-ldap_dn_filter is undefined.
-Example:
-
{ldap_dn_filter, {"(&(name=%s)(owner=%D)(user=%u@%d))", ["sn"]}}.
-Since this filter makes additional LDAP lookups, use it only in the
-last resort: try to define all filter rules in ldap_filter if possible.
- - {ldap_local_filter, Filter}
-
-If you can’t use ldap_filter due to performance reasons
-(the LDAP server has many users registered),
-you can use this local filter.
-The local filter checks an attribute in ejabberd,
-not in LDAP, so this limits the load on the LDAP directory.
-The default filter is: undefined.
-Example values:
-
{ldap_local_filter, {notequal, {"accountStatus",["disabled"]}}}.
-{ldap_local_filter, {equal, {"accountStatus",["enabled"]}}}.
-{ldap_local_filter, undefined}.
-
-
-
Let’s say ldap.example.org is the name of our LDAP server. We have
-users with their passwords in "ou=Users,dc=example,dc=org" directory.
-Also we have addressbook, which contains users emails and their additional
-infos in "ou=AddressBook,dc=example,dc=org" directory.
-The connection to the LDAP server is encrypted using TLS,
-and using the custom port 6123.
-Corresponding authentication section should looks like this:
%% Authentication method
-{auth_method, ldap}.
-%% DNS name of our LDAP server
-{ldap_servers, ["ldap.example.org"]}.
-%% Bind to LDAP server as "cn=Manager,dc=example,dc=org" with password "secret"
-{ldap_rootdn, "cn=Manager,dc=example,dc=org"}.
-{ldap_password, "secret"}.
-{ldap_encrypt, tls}.
-{ldap_port, 6123}.
-%% Define the user's base
-{ldap_base, "ou=Users,dc=example,dc=org"}.
-%% We want to authorize users from 'shadowAccount' object class only
-{ldap_filter, "(objectClass=shadowAccount)"}.
-Now we want to use users LDAP-info as their vCards. We have four attributes
-defined in our LDAP schema: "mail" — email address, "givenName"
-— first name, "sn" — second name, "birthDay" — birthday.
-Also we want users to search each other. Let’s see how we can set it up:
{modules,
- [
- ...
- {mod_vcard_ldap,
- [
- %% We use the same server and port, but want to bind anonymously because
- %% our LDAP server accepts anonymous requests to
- %% "ou=AddressBook,dc=example,dc=org" subtree.
- {ldap_rootdn, ""},
- {ldap_password, ""},
- %% define the addressbook's base
- {ldap_base, "ou=AddressBook,dc=example,dc=org"},
- %% uidattr: user's part of JID is located in the "mail" attribute
- %% uidattr_format: common format for our emails
- {ldap_uids, [{"mail", "%u@mail.example.org"}]},
- %% We have to define empty filter here, because entries in addressbook does not
- %% belong to shadowAccount object class
- {ldap_filter, ""},
- %% Now we want to define vCard pattern
- {ldap_vcard_map,
- [{"NICKNAME", "%u", []}, % just use user's part of JID as his nickname
- {"GIVEN", "%s", ["givenName"]},
- {"FAMILY", "%s", ["sn"]},
- {"FN", "%s, %s", ["sn", "givenName"]}, % example: "Smith, John"
- {"EMAIL", "%s", ["mail"]},
- {"BDAY", "%s", ["birthDay"]}]},
- %% Search form
- {ldap_search_fields,
- [{"User", "%u"},
- {"Name", "givenName"},
- {"Family Name", "sn"},
- {"Email", "mail"},
- {"Birthday", "birthDay"}]},
- %% vCard fields to be reported
- %% Note that JID is always returned with search results
- {ldap_search_reported,
- [{"Full Name", "FN"},
- {"Nickname", "NICKNAME"},
- {"Birthday", "BDAY"}]}
- ]},
- ...
- ]}.
-Note that mod_vcard_ldap module checks for the existence of the user before
-searching in his information in LDAP.
-
-
Active Directory is just an LDAP-server with predefined attributes. A sample
-configuration is shown below:
{auth_method, ldap}.
-{ldap_servers, ["office.org"]}. % List of LDAP servers
-{ldap_base, "DC=office,DC=org"}. % Search base of LDAP directory
-{ldap_rootdn, "CN=Administrator,CN=Users,DC=office,DC=org"}. % LDAP manager
-{ldap_password, "*******"}. % Password to LDAP manager
-{ldap_uids, [{"sAMAccountName"}]}.
-{ldap_filter, "(memberOf=*)"}.
-
-{modules,
- [
- ...
- {mod_vcard_ldap,
- [{ldap_vcard_map,
- [{"NICKNAME", "%u", []},
- {"GIVEN", "%s", ["givenName"]},
- {"MIDDLE", "%s", ["initials"]},
- {"FAMILY", "%s", ["sn"]},
- {"FN", "%s", ["displayName"]},
- {"EMAIL", "%s", ["mail"]},
- {"ORGNAME", "%s", ["company"]},
- {"ORGUNIT", "%s", ["department"]},
- {"CTRY", "%s", ["c"]},
- {"LOCALITY", "%s", ["l"]},
- {"STREET", "%s", ["streetAddress"]},
- {"REGION", "%s", ["st"]},
- {"PCODE", "%s", ["postalCode"]},
- {"TITLE", "%s", ["title"]},
- {"URL", "%s", ["wWWHomePage"]},
- {"DESC", "%s", ["description"]},
- {"TEL", "%s", ["telephoneNumber"]}]},
- {ldap_search_fields,
- [{"User", "%u"},
- {"Name", "givenName"},
- {"Family Name", "sn"},
- {"Email", "mail"},
- {"Company", "company"},
- {"Department", "department"},
- {"Role", "title"},
- {"Description", "description"},
- {"Phone", "telephoneNumber"}]},
- {ldap_search_reported,
- [{"Full Name", "FN"},
- {"Nickname", "NICKNAME"},
- {"Email", "EMAIL"}]}
- ]},
- ...
- ]}.
-
-
-
The option modules defines the list of modules that will be loaded after
-ejabberd’s startup. Each entry in the list is a tuple in which the first
-element is the name of a module and the second is a list of options for that
-module.
The syntax is:
-
- {modules, [ {ModuleName, ModuleOptions}, ...]}.
Examples:
-
-
-In this example only the module mod_echo is loaded and no module
-options are specified between the square brackets:
-
{modules,
- [
- {mod_echo, []}
- ]}.
- - In the second example the modules mod_echo, mod_time, and
-mod_version are loaded without options. Remark that, besides the last entry,
-all entries end with a comma:
-
{modules,
- [
- {mod_echo, []},
- {mod_time, []},
- {mod_version, []}
- ]}.
-
-
-
The following table lists all modules included in ejabberd.
-
-(*) This module requires a supported database. For a list of supported databases, see section 3.2.
-
You can see which database backend each module needs by looking at the suffix:
-
-
-No suffix, this means that the modules uses Erlang’s built-in database
-Mnesia as backend, or in some cases it can be configured to use ODBC.
-
- ‘_odbc’, this means that the module needs a supported database
-(see 3.2) as backend.
-
- ‘_ldap’, this means that the module needs an LDAP server as backend.
-
Those modules accept the option {backend, mnesia|odbc},
-and can store the tables in the configured backend:
You can find more
-contributed modules on the
-ejabberd website. Please remember that these contributions might not work or
-that they can contain severe bugs and security leaks. Therefore, use them at
-your own risk!
-
The following options are used by many modules. Therefore, they are described in
-this separate section.
-
-
Many modules define handlers for processing IQ queries of different namespaces
-to this server or to a user (e. g. to example.org or to
-user@example.org). This option defines processing discipline for
-these queries.
The syntax is:
-
- {iqdisc, Value}
Possible Value are:
-
-
-no_queue
- All queries of a namespace with this processing discipline are
-processed immediately. This also means that no other packets can be processed
-until this one has been completely processed. Hence this discipline is not
-recommended if the processing of a query can take a relatively long time.
-
- one_queue
- In this case a separate queue is created for the processing
-of IQ queries of a namespace with this discipline. In addition, the processing
-of this queue is done in parallel with that of other packets. This discipline
-is most recommended.
-
- {queues, N}
- N separate queues are created to process the
-queries. The queries are thus process in parallel, but in a
-controlled way.
-
- parallel
- For every packet with this discipline a separate Erlang process
-is spawned. Consequently, all these packets are processed in parallel.
-Although spawning of Erlang process has a relatively low cost, this can break
-the server’s normal work, because the Erlang emulator has a limit on the
-number of processes (32000 by default).
-
Example:
-
{modules,
- [
- ...
- {mod_time, [{iqdisc, no_queue}]},
- ...
- ]}.
-
-
-
This option defines the Jabber ID of a service provided by an ejabberd module.
The syntax is:
-
- {host, HostName}
If you include the keyword "@HOST@" in the HostName,
-it is replaced at start time with the real virtual host string.
This example configures
-the echo module to provide its echoing service
-in the Jabber ID mirror.example.org:
-
{modules,
- [
- ...
- {mod_echo, [{host, "mirror.example.org"}]},
- ...
- ]}.
-However, if there are several virtual hosts and this module is enabled in all of them,
-the "@HOST@" keyword must be used:
-
{modules,
- [
- ...
- {mod_echo, [{host, "mirror.@HOST@"}]},
- ...
- ]}.
-
-
-
This module enables configured users to broadcast announcements and to set
-the message of the day (MOTD).
-Configured users can perform these actions with a
-XMPP client either using Ad-hoc commands
-or sending messages to specific JIDs.
The Ad-hoc commands are listed in the Server Discovery.
-For this feature to work, mod_adhoc must be enabled.
The specific JIDs where messages can be sent are listed bellow.
-The first JID in each entry will apply only to the specified virtual host
-example.org, while the JID between brackets will apply to all virtual
-hosts in ejabberd.
-
-
-example.org/announce/all (example.org/announce/all-hosts/all)
- The
-message is sent to all registered users. If the user is online and connected
-to several resources, only the resource with the highest priority will receive
-the message. If the registered user is not connected, the message will be
-stored offline in assumption that offline storage
-(see section 3.3.12) is enabled.
-
- example.org/announce/online (example.org/announce/all-hosts/online)
- The
-message is sent to all connected users. If the user is online and connected
-to several resources, all resources will receive the message.
-
- example.org/announce/motd (example.org/announce/all-hosts/motd)
- The
-message is set as the message of the day (MOTD) and is sent to users when they
-login. In addition the message is sent to all connected users (similar to
-announce/online).
-
- example.org/announce/motd/update (example.org/announce/all-hosts/motd/update)
-
-The message is set as message of the day (MOTD) and is sent to users when they
-login. The message is not sent to any currently connected user.
-
- example.org/announce/motd/delete (example.org/announce/all-hosts/motd/delete)
-
-Any message sent to this JID removes the existing message of the day (MOTD).
-
Options:
-
-
-{access, AccessName}
- This option specifies who is allowed to
-send announcements and to set the message of the day (by default, nobody is
-able to send such messages).
-
Examples:
-
-
-Only administrators can send announcements:
-
{access, announce, [{allow, admins}]}.
-
-{modules,
- [
- ...
- {mod_adhoc, []},
- {mod_announce, [{access, announce}]},
- ...
- ]}.
- - Administrators as well as the direction can send announcements:
-
{acl, direction, {user, "big_boss", "example.org"}}.
-{acl, direction, {user, "assistant", "example.org"}}.
-{acl, admins, {user, "admin", "example.org"}}.
-
-{access, announce, [{allow, admins},
- {allow, direction}]}.
-
-{modules,
- [
- ...
- {mod_adhoc, []},
- {mod_announce, [{access, announce}]},
- ...
- ]}.
-
Note that mod_announce can be resource intensive on large
-deployments as it can broadcast lot of messages. This module should be
-disabled for instances of ejabberd with hundreds of thousands users.
-
-
-
-
-
-
This module adds support for Service Discovery (XEP-0030). With
-this module enabled, services on your server can be discovered by
-XMPP clients. Note that ejabberd has no modules with support
-for the superseded Jabber Browsing (XEP-0011) and Agent Information
-(XEP-0094). Accordingly, XMPP clients need to have support for
-the newer Service Discovery protocol if you want them be able to discover
-the services you offer.
Options:
-
-
-{iqdisc, Discipline}
- This specifies
-the processing discipline for Service Discovery (http://jabber.org/protocol/disco#items and
-http://jabber.org/protocol/disco#info) IQ queries (see section 3.3.2).
-
- {extra_domains, [Domain, ...]}
- With this option,
-you can specify a list of extra domains that are added to the Service Discovery item list.
-
- {server_info, [ {Modules, Field, [Value, ...]}, ... ]}
-
-Specify additional information about the server,
-as described in Contact Addresses for XMPP Services (XEP-0157).
-Modules can be the keyword ‘all’,
-in which case the information is reported in all the services;
-or a list of ejabberd modules,
-in which case the information is only specified for the services provided by those modules.
-Any arbitrary Field and Value can be specified, not only contact addresses.
-
Examples:
-
-
-To serve a link to the Jabber User Directory on jabber.org:
-
{modules,
- [
- ...
- {mod_disco, [{extra_domains, ["users.jabber.org"]}]},
- ...
- ]}.
- - To serve a link to the transports on another server:
-
{modules,
- [
- ...
- {mod_disco, [{extra_domains, ["icq.example.com",
- "msn.example.com"]}]},
- ...
- ]}.
- - To serve a link to a few friendly servers:
-
{modules,
- [
- ...
- {mod_disco, [{extra_domains, ["example.org",
- "example.com"]}]},
- ...
- ]}.
- - With this configuration, all services show abuse addresses,
-feedback address on the main server,
-and admin addresses for both the main server and the vJUD service:
-
{modules,
- [
- ...
- {mod_disco, [{server_info, [
- {all,
- "abuse-addresses",
- ["mailto:abuse@shakespeare.lit"]},
- {[mod_muc],
- "Web chatroom logs",
- ["http://www.example.org/muc-logs"]},
- {[mod_disco],
- "feedback-addresses",
- ["http://shakespeare.lit/feedback.php", "mailto:feedback@shakespeare.lit", "xmpp:feedback@shakespeare.lit"]},
- {[mod_disco, mod_vcard],
- "admin-addresses",
- ["mailto:xmpp@shakespeare.lit", "xmpp:admins@shakespeare.lit"]}
- ]}]},
- ...
- ]}.
-
-
-
This module simply echoes any XMPP
-packet back to the sender. This mirror can be of interest for
-ejabberd and XMPP client debugging.
Options:
-
-
-
-{host, HostName}
- This option defines the Jabber ID of the
-service. If the host option is not specified, the Jabber ID will be the
-hostname of the virtual host with the prefix ‘echo.’. The keyword "@HOST@"
-is replaced at start time with the real virtual host name.
-
-
Example: Mirror, mirror, on the wall, who is the most beautiful
-of them all?
-
{modules,
- [
- ...
- {mod_echo, [{host, "mirror.example.org"}]},
- ...
- ]}.
-
-
-
This module implements XMPP over Bosh (formerly known as HTTP Binding)
-as defined in XEP-0124 and XEP-0206.
-It extends ejabberd’s built in HTTP service with a configurable
-resource at which this service will be hosted.
To use HTTP-Binding, enable the module:
-
{modules,
- [
- ...
- {mod_http_bind, []},
- ...
-]}.
-and add http_bind in the HTTP service. For example:
-
{listen,
- [
- ...
- {5280, ejabberd_http, [
- http_bind,
- http_poll,
- web_admin
- ]
- },
- ...
-]}.
-With this configuration, the module will serve the requests sent to
-http://example.org:5280/http-bind/
-Remember that this page is not designed to be used by web browsers,
-it is used by XMPP clients that support XMPP over Bosh.
If you want to set the service in a different URI path or use a different module,
-you can configure it manually using the option request_handlers.
-For example:
-
{listen,
- [
- ...
- {5280, ejabberd_http, [
- {request_handlers, [{["http-bind"], mod_http_bind}]},
- http_poll,
- web_admin
- ]
- },
- ...
-]}.
-Options:
-
-
-{max_inactivity, Seconds}
-
-Define the maximum inactivity period in seconds.
-Default value is 30 seconds.
-For example, to set 50 seconds:
-
{modules,
- [
- ...
- {mod_http_bind, [ {max_inactivity, 50} ]},
- ...
-]}.
-
-
-
This simple module serves files from the local disk over HTTP.
Options:
-
-
-{docroot, Path}
-
-Directory to serve the files.
-
- {accesslog, Path}
-
-File to log accesses using an Apache-like format.
-No log will be recorded if this option is not specified.
-
- {directory_indices, [Index, ...]}
-
-Indicate one or more directory index files, similarly to Apache’s
-DirectoryIndex variable. When a web request hits a directory
-instead of a regular file, those directory indices are looked in
-order, and the first one found is returned.
-
- {custom_headers, [ {Name, Value}, ...]}
-
-Indicate custom HTTP headers to be included in all responses.
-Default value is: []
-
- {content_types, [ {Name, Type}, ...]}
-
-Specify mappings of extension to content type.
-There are several content types already defined,
-with this option you can add new definitions, modify or delete existing ones.
-To delete an existing definition, simply define it with a value: ‘undefined’.
-
- {default_content_type, Type}
-
-Specify the content type to use for unknown extensions.
-Default value is ‘application/octet-stream’.
-
This example configuration will serve the files from
-the local directory /var/www
-in the address http://example.org:5280/pub/archive/.
-In this example a new content type ogg is defined,
-png is redefined, and jpg definition is deleted.
-To use this module you must enable it:
-
{modules,
- [
- ...
- {mod_http_fileserver, [
- {docroot, "/var/www"},
- {accesslog, "/var/log/ejabberd/access.log"},
- {directory_indices, ["index.html", "main.htm"]},
- {custom_headers, [{"X-Powered-By", "Erlang/OTP"},
- {"X-Fry", "It's a widely-believed fact!"}
- ]},
- {content_types, [{".ogg", "audio/ogg"},
- {".png", "image/png"},
- {".jpg", undefined}
- ]},
- {default_content_type, "text/html"}
- ]
- },
- ...
-]}.
-And define it as a handler in the HTTP service:
-
{listen,
- [
- ...
- {5280, ejabberd_http, [
- ...
- {request_handlers, [
- ...
- {["pub", "archive"], mod_http_fileserver},
- ...
- ]
- },
- ...
- ]
- },
- ...
-]}.
-
-
-
This module adds support for Last Activity (XEP-0012). It can be used to
-discover when a disconnected user last accessed the server, to know when a
-connected user was last active on the server, or to query the uptime of the
-ejabberd server.
Options:
-
-
-{backend, mnesia|odbc}
-
-Specify the backend used to store the tables: last_activity.
-The default value is mnesia.
-If configured to odbc, then you must also configure in ejabberd
-the database connection (see the subsections of 3.2).
-
-
- {iqdisc, Discipline}
- This specifies
-the processing discipline for Last activity (jabber:iq:last) IQ queries (see section 3.3.2).
-
-
-
This module provides a Multi-User Chat (XEP-0045) service.
-Users can discover existing rooms, join or create them.
-Occupants of a room can chat in public or have private chats.
Some of the features of Multi-User Chat:
-
-
-Sending public and private messages to room occupants.
-
- Inviting other users to a room.
-
- Setting a room subject.
-
- Creating password protected rooms.
-
- Kicking and banning occupants.
-
The MUC service allows any Jabber ID to register a nickname,
-so nobody else can use that nickname in any room in the MUC service.
-To register a nickname, open the Service Discovery in your
-XMPP client and register in the MUC service.
This module supports clustering and load
-balancing. One module can be started per cluster node. Rooms are
-distributed at creation time on all available MUC module
-instances. The multi-user chat module is clustered but the rooms
-themselves are not clustered nor fault-tolerant: if the node managing a
-set of rooms goes down, the rooms disappear and they will be recreated
-on an available node on first connection attempt.
Module options:
-
-
-
-{host, HostName}
- This option defines the Jabber ID of the
-service. If the host option is not specified, the Jabber ID will be the
-hostname of the virtual host with the prefix ‘conference.’. The keyword "@HOST@"
-is replaced at start time with the real virtual host name.
-
-
- {access, AccessName}
- You can specify who is allowed to use
-the Multi-User Chat service. By default everyone is allowed to use it.
-
- {access_create, AccessName}
- To configure who is
-allowed to create new rooms at the Multi-User Chat service, this option can be used.
-By default any account in the local ejabberd server is allowed to create rooms.
-
- {access_persistent, AccessName}
- To configure who is
-allowed to modify the ’persistent’ room option.
-By default any account in the local ejabberd server is allowed to modify that option.
-
- {access_admin, AccessName}
- This option specifies
-who is allowed to administrate the Multi-User Chat service. The default
-value is none, which means that only the room creator can
-administer his room.
-The administrators can send a normal message to the service JID,
-and it will be shown in all active rooms as a service message.
-The administrators can send a groupchat message to the JID of an active room,
-and the message will be shown in the room as a service message.
-
- {history_size, Size}
- A small history of
-the current discussion is sent to users when they enter the
-room. With this option you can define the number of history messages
-to keep and send to users joining the room. The value is an
-integer. Setting the value to 0 disables the history feature
-and, as a result, nothing is kept in memory. The default value is
-20. This value is global and thus affects all rooms on the
-service.
-
- {max_users, Number}
- This option defines at
-the service level, the maximum number of users allowed per
-room. It can be lowered in each room configuration but cannot be
-increased in individual room configuration. The default value is
-200.
-
- {max_users_admin_threshold, Number}
-
- This option defines the
-number of service admins or room owners allowed to enter the room when
-the maximum number of allowed occupants was reached. The default limit
-is 5.
-
- {max_user_conferences, Number}
-
- This option defines the maximum
-number of rooms that any given user can join. The default value
-is 10. This option is used to prevent possible abuses. Note that
-this is a soft limit: some users can sometimes join more conferences
-in cluster configurations.
-
- {max_room_id, Number}
-
-This option defines the maximum number of characters that Room ID
-can have when creating a new room.
-The default value is to not limit: infinite.
-
- {max_room_name, Number}
-
-This option defines the maximum number of characters that Room Name
-can have when configuring the room.
-The default value is to not limit: infinite.
-
- {max_room_desc, Number}
-
-This option defines the maximum number of characters that Room Description
-can have when configuring the room.
-The default value is to not limit: infinite.
-
- {min_message_interval, Number}
-
-This option defines the minimum interval between two messages send
-by an occupant in seconds. This option is global and valid for all
-rooms. A decimal value can be used. When this option is not defined,
-message rate is not limited. This feature can be used to protect a
-MUC service from occupant abuses and limit number of messages that will
-be broadcasted by the service. A good value for this minimum message
-interval is 0.4 second. If an occupant tries to send messages faster, an
-error is send back explaining that the message has been discarded
-and describing the reason why the message is not acceptable.
-
- {min_presence_interval, Number}
-
- This option defines the
-minimum of time between presence changes coming from a given occupant in
-seconds. This option is global and valid for all rooms. A
-decimal value can be used. When this option is not defined, no
-restriction is applied. This option can be used to protect a MUC
-service for occupants abuses. If an occupant tries
-to change its presence more often than the specified interval, the
-presence is cached by ejabberd and only the last presence is
-broadcasted to all occupants in the room after expiration of the
-interval delay. Intermediate presence packets are silently
-discarded. A good value for this option is 4 seconds.
-
- {default_room_options, [ {OptionName, OptionValue}, ...]}
-
-This module option allows to define the desired default room options.
-Note that the creator of a room can modify the options of his room
-at any time using a XMPP client with MUC capability.
-The available room options and the default values are:
-
-
-{allow_change_subj, true|false}
- Allow occupants to change the subject.
-
- {allow_private_messages, true|false}
- Occupants can send private messages to other occupants.
-
- {allow_query_users, true|false}
- Occupants can send IQ queries to other occupants.
-
- {allow_user_invites, false|true}
- Allow occupants to send invitations.
-
- {allow_visitor_nickchange, true|false}
- Allow visitors to
-change nickname.
-
- {allow_visitor_status, true|false}
- Allow visitors to send
-status text in presence updates. If disallowed, the status
-text is stripped before broadcasting the presence update to all
-the room occupants.
-
- {anonymous, true|false}
- The room is anonymous:
-occupants don’t see the real JIDs of other occupants.
-Note that the room moderators can always see the real JIDs of the occupants.
-
- {captcha_protected, false}
-
-When a user tries to join a room where he has no affiliation (not owner, admin or member),
-the room requires him to fill a CAPTCHA challenge (see section 3.1.8)
-in order to accept her join in the room.
-
- {logging, false|true}
- The public messages are logged using mod_muc_log.
-
- {max_users, 200}
- Maximum number of occupants in the room.
-
- {members_by_default, true|false}
- The occupants that enter the room are participants by default, so they have ’voice’.
-
- {members_only, false|true}
- Only members of the room can enter.
-
- {moderated, true|false}
- Only occupants with ’voice’ can send public messages.
-
- {password, "roompass123"}
- Password of the room. You may want to enable the next option too.
-
- {password_protected, false|true}
- The password is required to enter the room.
-
- {persistent, false|true}
- The room persists even if the last participant leaves.
-
- {public, true|false}
- The room is public in the list of the MUC service, so it can be discovered.
-
- {public_list, true|false}
- The list of participants is public, without requiring to enter the room.
-
- {title, "Room Title"}
- A human-readable title of the room.
-
-All of those room options can be set to true or false,
-except password and title which are strings,
-and max_users that is integer.
-
Examples:
-
-
-In the first example everyone is allowed to use the Multi-User Chat
-service. Everyone will also be able to create new rooms but only the user
-admin@example.org is allowed to administrate any room. In this
-example he is also a global administrator. When admin@example.org
-sends a message such as ‘Tomorrow, the XMPP server will be moved
-to new hardware. This will involve service breakdowns around 23:00 UMT.
-We apologise for this inconvenience.’ to conference.example.org,
-it will be displayed in all active rooms. In this example the history
-feature is disabled.
-
{acl, admin, {user, "admin", "example.org"}}.
-
-{access, muc_admin, [{allow, admin}]}.
-
-{modules,
- [
- ...
- {mod_muc, [{access, all},
- {access_create, all},
- {access_admin, muc_admin},
- {history_size, 0}]},
- ...
- ]}.
- - In the second example the Multi-User Chat service is only accessible by
-paying customers registered on our domains and on other servers. Of course
-the administrator is also allowed to access rooms. In addition, he is the
-only authority able to create and administer rooms. When
-admin@example.org sends a message such as ‘Tomorrow, the Jabber
-server will be moved to new hardware. This will involve service breakdowns
-around 23:00 UMT. We apologise for this inconvenience.’ to
-conference.example.org, it will be displayed in all active rooms. No
-history_size option is used, this means that the feature is enabled
-and the default value of 20 history messages will be send to the users.
-
{acl, paying_customers, {user, "customer1", "example.net"}}.
-{acl, paying_customers, {user, "customer2", "example.com"}}.
-{acl, paying_customers, {user, "customer3", "example.org"}}.
-{acl, admin, {user, "admin", "example.org"}}.
-
-{access, muc_admin, [{allow, admin},
- {deny, all}]}.
-{access, muc_access, [{allow, paying_customers},
- {allow, admin},
- {deny, all}]}.
-
-{modules,
- [
- ...
- {mod_muc, [{access, muc_access},
- {access_create, muc_admin},
- {access_admin, muc_admin}]},
- ...
- ]}.
- - In the following example, MUC anti abuse options are used. An
-occupant cannot send more than one message every 0.4 seconds and cannot
-change its presence more than once every 4 seconds.
-The length of Room IDs and Room Names are limited to 20 characters,
-and Room Description to 300 characters. No ACLs are
-defined, but some user restriction could be added as well:
{modules,
- [
- ...
- {mod_muc, [{min_message_interval, 0.4},
- {min_presence_interval, 4},
- {max_room_id, 20},
- {max_room_name, 20},
- {max_room_desc, 300}]},
- ...
- ]}.
- - This example shows how to use default_room_options to make sure
-the newly created rooms have by default those options.
-
{modules,
- [
- ...
- {mod_muc, [{access, muc_access},
- {access_create, muc_admin},
- {default_room_options,
- [
- {allow_change_subj, false},
- {allow_query_users, true},
- {allow_private_messages, true},
- {members_by_default, false},
- {title, "New chatroom"},
- {anonymous, false}
- ]},
- {access_admin, muc_admin}]},
- ...
- ]}.
-
-
-
This module enables optional logging of Multi-User Chat (MUC) public conversations to
-HTML. Once you enable this module, users can join a room using a MUC capable
-XMPP client, and if they have enough privileges, they can request the
-configuration form in which they can set the option to enable room logging.
Features:
-
-
-Room details are added on top of each page: room title, JID,
-author, subject and configuration.
-
-
-The room JID in the generated HTML is a link to join the room (using
-XMPP URI).
-
- Subject and room configuration changes are tracked and displayed.
-
- Joins, leaves, nick changes, kicks, bans and ‘/me’ are tracked and
-displayed, including the reason if available.
-
- Generated HTML files are XHTML 1.0 Transitional and CSS compliant.
-
- Timestamps are self-referencing links.
-
- Links on top for quicker navigation: Previous day, Next day, Up.
-
- CSS is used for style definition, and a custom CSS file can be used.
-
- URLs on messages and subjects are converted to hyperlinks.
-
- Timezone used on timestamps is shown on the log files.
-
- A custom link can be added on top of each page.
-
Options:
-
-
-{access_log, AccessName}
-
-This option restricts which occupants are allowed to enable or disable room
-logging. The default value is muc_admin. Note for this default setting
-you need to have an access rule for muc_admin in order to take effect.
-
- {cssfile, false|URL}
-
-With this option you can set whether the HTML files should have a custom CSS
-file or if they need to use the embedded CSS file. Allowed values are
-false and an URL to a CSS file. With the first value, HTML files will
-include the embedded CSS code. With the latter, you can specify the URL of the
-custom CSS file (for example: "http://example.com/my.css"). The default value
-is false.
-
- {dirname, room_jid|room_name}
-
-Allows to configure the name of the room directory.
-Allowed values are room_jid and room_name.
-With the first value, the room directory name will be the full room JID.
-With the latter, the room directory name will be only the room name,
-not including the MUC service name.
-The default value is room_jid.
-
- {dirtype, subdirs|plain}
-
-The type of the created directories can be specified with this option. Allowed
-values are subdirs and plain. With the first value,
-subdirectories are created for each year and month. With the latter, the
-names of the log files contain the full date, and there are no subdirectories.
-The default value is subdirs.
-
- {file_format, html|plaintext}
-
-Define the format of the log files:
-html stores in HTML format,
-plaintext stores in plain text.
-The default value is html.
-
- {outdir, Path}
-
-This option sets the full path to the directory in which the HTML files should
-be stored. Make sure the ejabberd daemon user has write access on that
-directory. The default value is "www/muc".
-
- {link_nofollow true|false}
-
-The option link_nofollow adds a special attribute
-to links that prevent their indexation by search engines. The default value
-is true, which means that nofollow attributes will be added to user
-submitted links.
-
- {timezone, local|universal}
-
-The time zone for the logs is configurable with this option. Allowed values
-are local and universal. With the first value, the local time,
-as reported to Erlang by the operating system, will be used. With the latter,
-GMT/UTC time will be used. The default value is local.
-
- {top_link, {URL, Text}}
-
-With this option you can customize the link on the top right corner of each
-log file. The default value is {"/", "Home"}.
-
Examples:
-
-
-In the first example any room owner can enable logging, and a
-custom CSS file will be used (http://example.com/my.css). The names
-of the log files will contain the full date, and there will be no
-subdirectories. The log files will be stored in /var/www/muclogs, and the
-time zone will be GMT/UTC. Finally, the top link will be
-
<a href="http://www.jabber.ru/">Jabber.ru</a>.
-{access, muc, [{allow, all}]}.
-
-{modules,
- [
- ...
- {mod_muc_log, [
- {access_log, muc},
- {cssfile, "http://example.com/my.css"},
- {dirtype, plain},
- {dirname, room_jid},
- {outdir, "/var/www/muclogs"},
- {timezone, universal},
- {link_nofollow, true},
- {top_link, {"http://www.jabber.ru/", "Jabber.ru"}}
- ]},
- ...
- ]}.
- - In the second example only admin1@example.org and
-admin2@example.net can enable logging, and the embedded CSS file will be
-used. The names of the log files will only contain the day (number),
-and there will be subdirectories for each year and month. The log files will
-be stored in /var/www/muclogs, and the local time will be used. Finally, the
-top link will be the default
<a href="/">Home</a>.
-{acl, admins, {user, "admin1", "example.org"}}.
-{acl, admins, {user, "admin2", "example.net"}}.
-
-{access, muc_log, [{allow, admins},
- {deny, all}]}.
-
-{modules,
- [
- ...
- {mod_muc_log, [
- {access_log, muc_log},
- {cssfile, false},
- {dirtype, subdirs},
- {outdir, "/var/www/muclogs"},
- {timezone, local}
- ]},
- ...
- ]}.
-
-
-
This module implements a service for Extended Stanza Addressing (XEP-0033)
-that can be used by local or remote XMPP entities (users, components or servers).
-If this service is enabled, it will be used by ejabberd to send
-C2S presence broadcasts, and MUC groupchat messages.
Options:
-
-
-
-{host, HostName}
- This option defines the Jabber ID of the
-service. If the host option is not specified, the Jabber ID will be the
-hostname of the virtual host with the prefix ‘multicast.’. The keyword "@HOST@"
-is replaced at start time with the real virtual host name.
-
-
- {access, AccessName}
-
-Specify who can send packets to the multicast service.
-By default everyone is allowed to use it.
-
- {limits, [ {Sender, Stanza, Number} ] }
-
-Specify a list of custom limits which override the default ones.
-Sender can be local or remote.
-Stanza can be message or presence.
-Number can be a positive integer or the key word infinite.
-The default value of this option is:
-
[{local, message, 100},
- {local, presence, 100},
- {remote, message, 20},
- {remote, presence, 20}]
-
Example configuration:
-
% Only admins can send packets to multicast service
-{access, multicast, [{allow, admin}, {deny, all}]}.
-
-% If you want to allow all your users:
-%{access, multicast, [{allow, all}]}.
-
-% This allows both admins and remote users to send packets,
-% but does not allow local users:
-%{acl, allservers, {server_glob, "*"}}.
-%{access, multicast, [{allow, admin}, {deny, local}, {allow, allservers}]}.
-
-{modules, [
- ...
- {mod_multicast, [
- {host, "multicast.example.org"},
- {access, multicast},
- {limits, [
- {local, message, 40},
- {local, presence, infinite},
- {remote, message, 150}
- ]}
- ]},
- ...
-]}.
-
-
-
This module implements offline message storage (XEP-0160).
-This means that all messages
-sent to an offline user will be stored on the server until that user comes
-online again. Thus it is very similar to how email works. Note that
-ejabberdctl has a command to delete expired messages
-(see section 4.1).
-
-{access_max_user_messages, AccessName}
-
-This option defines which access rule will be enforced to limit
-the maximum number of offline messages that a user can have (quota).
-When a user has too many offline messages, any new messages that he receive are discarded,
-and a resource-constraint error is returned to the sender.
-The default value is max_user_offline_messages.
-Then you can define an access rule with a syntax similar to
-
- {backend, mnesia|odbc}
-
-Specify the backend used to store the tables: offline_msg.
-The default value is mnesia.
-If configured to odbc, then you must also configure in ejabberd
-the database connection (see the subsections of 3.2).
-
-max_user_sessions (see 3.1.5).
-
This example allows power users to have as much as 5000 offline messages,
-administrators up to 2000,
-and all the other users up to 100.
-
{acl, admin, {user, "admin1", "localhost"}}.
-{acl, admin, {user, "admin2", "example.org"}}.
-{acl, poweruser, {user, "bob", "example.org"}}.
-{acl, poweruser, {user, "jane", "example.org"}}.
-
-{access, max_user_offline_messages, [ {5000, poweruser}, {2000, admin}, {100, all} ]}.
-
-{modules,
- [
- ...
- {mod_offline, [ {access_max_user_messages, max_user_offline_messages} ]},
- ...
- ]}.
-
-
-
This module implements support for XMPP Ping (XEP-0199) and periodic keepalives.
-When this module is enabled ejabberd responds correctly to
-ping requests, as defined in the protocol.
Configuration options:
-
-
-{send_pings, true|false}
-
-If this option is set to true, the server sends pings to connected clients
-that are not active in a given interval ping_interval.
-This is useful to keep client connections alive or checking availability.
-By default this option is disabled.
-
- {ping_interval, Seconds}
-
-How often to send pings to connected clients, if the previous option is enabled.
-If a client connection does not send or receive any stanza in this interval,
-a ping request is sent to the client.
-The default value is 60 seconds.
-
- {timeout_action, none|kill}
-
-What to do when a client does not answer to a server ping request in less than 32 seconds.
-The default is to do nothing.
-
This example enables Ping responses, configures the module to send pings
-to client connections that are inactive for 4 minutes,
-and if a client does not answer to the ping in less than 32 seconds, its connection is closed:
-
{modules,
- [
- ...
- {mod_ping, [{send_pings, true}, {ping_interval, 240}, {timeout_action, kill}]},
- ...
- ]}.
-
-
-
This module implements Blocking Communication (also known as Privacy Rules)
-as defined in section 10 from XMPP IM. If end users have support for it in
-their XMPP client, they will be able to:
-
--
-Retrieving one’s privacy lists.
-
- Adding, removing, and editing one’s privacy lists.
-
- Setting, changing, or declining active lists.
-
- Setting, changing, or declining the default list (i.e., the list that
-is active by default).
-
- Allowing or blocking messages based on JID, group, or subscription type
-(or globally).
-
- Allowing or blocking inbound presence notifications based on JID, group,
-or subscription type (or globally).
-
- Allowing or blocking outbound presence notifications based on JID, group,
-or subscription type (or globally).
-
- Allowing or blocking IQ stanzas based on JID, group, or subscription type
-(or globally).
-
- Allowing or blocking all communications based on JID, group, or
-subscription type (or globally).
-
-(from http://xmpp.org/rfcs/rfc3921.html#privacy)
-
Options:
-
-
-{backend, mnesia|odbc}
-
-Specify the backend used to store the tables: privacy_default_list, privacy_list and privacy_list_data.
-The default value is mnesia.
-If configured to odbc, then you must also configure in ejabberd
-the database connection (see the subsections of 3.2).
-
-
- {iqdisc, Discipline}
- This specifies
-the processing discipline for Blocking Communication (jabber:iq:privacy) IQ queries (see section 3.3.2).
-
-
-
This module adds support for Private XML Storage (XEP-0049):
-
-Using this method, XMPP entities can store private data on the server and
-retrieve it whenever necessary. The data stored might be anything, as long as
-it is valid XML. One typical usage for this namespace is the server-side storage
-of client-specific preferences; another is Bookmark Storage (XEP-0048).
-
Options:
-
-
-{backend, mnesia|odbc}
-
-Specify the backend used to store the tables: private_storage.
-The default value is mnesia.
-If configured to odbc, then you must also configure in ejabberd
-the database connection (see the subsections of 3.2).
-
-
- {iqdisc, Discipline}
- This specifies
-the processing discipline for Private XML Storage (jabber:iq:private) IQ queries (see section 3.3.2).
-
-
-
This module implements SOCKS5 Bytestreams (XEP-0065).
-It allows ejabberd to act as a file transfer proxy between two
-XMPP clients.
Options:
-
-
-
-{host, HostName}
- This option defines the Jabber ID of the
-service. If the host option is not specified, the Jabber ID will be the
-hostname of the virtual host with the prefix ‘proxy.’. The keyword "@HOST@"
-is replaced at start time with the real virtual host name.
-
-
- {name, Text}
- Defines Service Discovery name of the service.
-Default is "SOCKS5 Bytestreams".
-
- {ip, IPTuple}
- This option specifies which network interface
-to listen for. Default is an IP address of the service’s DNS name, or,
-if fails,
{127,0,0,1}.
- - {port, Number}
- This option defines port to listen for
-incoming connections. Default is 7777.
-
- {hostname, HostName}
- Defines a hostname advertised
-by the service when establishing a session with clients. This is useful when
-you run the service behind a NAT. The default is the value of ip option.
-Examples: "proxy.mydomain.org", "200.150.100.50". Note that
-not all clients understand domain names in stream negotiation,
-so you should think twice before setting domain name in this option.
-
- {auth_type, anonymous|plain}
- SOCKS5 authentication type.
-Possible values are anonymous and plain. Default is
-anonymous.
-
- {access, AccessName}
- Defines ACL for file transfer initiators.
-Default is all.
-
- {max_connections, Number}
- Maximum number of
-active connections per file transfer initiator. No limit by default.
-
- {shaper, none|ShaperName}
- This option defines shaper for
-the file transfer peers. Shaper with the maximum bandwidth will be selected.
-Default is none.
-
Examples:
-
-
-The simpliest configuration of the module:
-
{modules,
- [
- ...
- {mod_proxy65, []},
- ...
- ]}.
- - More complicated configuration.
-
{acl, proxy_users, {server, "example.org"}}.
-{access, proxy65_access, [{allow, proxy_users}, {deny, all}]}.
-
-{acl, admin, {user, "admin", "example.org"}}.
-{shaper, proxyrate, {maxrate, 10240}}. %% 10 Kbytes/sec
-{access, proxy65_shaper, [{none, admin}, {proxyrate, proxy_users}]}.
-
-{modules,
- [
- ...
- {mod_proxy65, [{host, "proxy1.example.org"},
- {name, "File Transfer Proxy"},
- {ip, {200,150,100,1}},
- {port, 7778},
- {max_connections, 5},
- {access, proxy65_access},
- {shaper, proxy65_shaper}]},
- ...
- ]}.
-
-
-
This module offers a Publish-Subscribe Service (XEP-0060).
-The functionality in mod_pubsub can be extended using plugins.
-The plugin that implements PEP (Personal Eventing via Pubsub) (XEP-0163)
-is enabled in the default ejabberd configuration file,
-and it requires mod_caps.
Options:
-
-
-
-{host, HostName}
- This option defines the Jabber ID of the
-service. If the host option is not specified, the Jabber ID will be the
-hostname of the virtual host with the prefix ‘pubsub.’. The keyword "@HOST@"
-is replaced at start time with the real virtual host name.
-
-If you use mod_pubsub_odbc, please ensure the prefix contains only one dot,
-for example ‘pubsub.’, or ‘publish.’,.
-
- {access_createnode, AccessName}
-
-This option restricts which users are allowed to create pubsub nodes using
-ACL and ACCESS.
-By default any account in the local ejabberd server is allowed to create pubsub nodes.
-
- {max_items_node, MaxItems}
-
-Define the maximum number of items that can be stored in a node.
-Default value is 10.
-
- {plugins, [ Plugin, ...]}
-
-To specify which pubsub node plugins to use. If not defined, the default
-pubsub plugin is always used.
-
- {nodetree, Name}
-
-To specify which nodetree to use. If not defined, the default pubsub
-nodetree is used. Only one nodetree can be used per host,
-and is shared by all node plugins.
-
- {ignore_pep_from_offline, false|true}
-
-To specify whether or not we should get last published PEP items
-from users in our roster which are offline when we connect. Value is true or false.
-If not defined, pubsub assumes true so we only get last items of online contacts.
-
- {last_item_cache, false|true}
-
-To specify whether or not pubsub should cache last items. Value is true
-or false. If not defined, pubsub do not cache last items. On systems with not so many nodes,
-caching last items speeds up pubsub and allows to raise user connection rate. The cost is memory
-usage, as every item is stored in memory.
-
- {pep_mapping, [ {Key, Value}, ...]}
-
-This allow to define a Key-Value list to choose defined node plugins on given PEP namespace.
-The following example will use node_tune instead of node_pep for every PEP node with tune namespace:
-
{mod_pubsub, [{pep_mapping, [{"http://jabber.org/protocol/tune", "tune"}]}]}
-
Example of configuration that uses flat nodes as default, and allows use of flat, nodetree and pep nodes:
-
{modules,
- [
- ...
- {mod_pubsub, [
- {access_createnode, pubsub_createnode},
- {plugins, ["flat", "hometree", "pep"]}
- ]},
- ...
- ]}.
-Using ODBC database requires use of dedicated plugins. The following example shows previous configuration
-with ODBC usage:
-
{modules,
- [
- ...
- {mod_pubsub_odbc, [
- {access_createnode, pubsub_createnode},
- {plugins, ["flat_odbc", "hometree_odbc", "pep_odbc"]}
- ]},
- ...
- ]}.
-
-
-
This module adds support for In-Band Registration (XEP-0077). This protocol
-enables end users to use a XMPP client to:
-
-
-Register a new account on the server.
-
- Change the password from an existing account on the server.
-
- Delete an existing account on the server.
-
Options:
-
-
-{access, AccessName}
- This option can be configured to specify
-rules to restrict registration. If a rule returns ‘deny’ on the requested
-user name, registration for that user name is denied. (there are no
-restrictions by default).
-
- {access_from, AccessName}
- By default, ejabberd
-doesn’t allow to register new accounts from s2s or existing c2s sessions. You can
-change it by defining access rule in this option. Use with care: allowing registration
-from s2s leads to uncontrolled massive accounts creation by rogue users.
-
- {welcome_message, Message}
- Set a welcome message that
-is sent to each newly registered account. The first string is the subject, and
-the second string is the message body.
-In the body you can set a newline with the characters:
\n
- - {registration_watchers, [ JID, ...]}
- This option defines a
-list of JIDs which will be notified each time a new account is registered.
-
- {iqdisc, Discipline}
- This specifies
-the processing discipline for In-Band Registration (jabber:iq:register) IQ queries (see section 3.3.2).
-
This module reads also another option defined globally for the server:
-{registration_timeout, Timeout}.
-This option limits the frequency of registration from a given IP or username.
-So, a user that tries to register a new account from the same IP address or JID during
-this number of seconds after his previous registration
-will receive an error resource-constraint with the explanation:
-“Users are not allowed to register accounts so quickly”.
-The timeout is expressed in seconds, and it must be an integer.
-To disable this limitation,
-instead of an integer put a word like: infinity.
-Default value: 600 seconds.
Examples:
-
-
-Next example prohibits the registration of too short account names:
-
{acl, shortname, {user_glob, "?"}}.
-{acl, shortname, {user_glob, "??"}}.
-%% The same using regexp:
-%%{acl, shortname, {user_regexp, "^..?$"}}.
-
-{access, register, [{deny, shortname},
- {allow, all}]}.
-
-{modules,
- [
- ...
- {mod_register, [{access, register}]},
- ...
- ]}.
- - This configuration prohibits usage of In-Band Registration
-to create or delete accounts,
-but allows existing accounts to change the password:
-
{access, register, [{deny, all}]}.
-
-{modules,
- [
- ...
- {mod_register, [{access, register}]},
- ...
- ]}.
- - This configuration disables all In-Band Registration
-functionality: create, delete accounts and change password:
-
{modules,
- [
- ...
- %% {mod_register, [{access, register}]},
- ...
- ]}.
- - Define the welcome message and two registration watchers.
-Also define a registration timeout of one hour:
-
{registration_timeout, 3600}.
-{modules,
- [
- ...
- {mod_register,
- [
- {welcome_message, {"Welcome!", "Hi.\nWelcome to this Jabber server.\n Check http://www.jabber.org\n\nBye"}},
- {registration_watchers, ["admin1@example.org", "boss@example.net"]}
- ]},
- ...
- ]}.
-
-
-
This module implements roster management as defined in
-RFC 3921: XMPP IM.
-It also supports Roster Versioning (XEP-0237).
Options:
-
-
-{backend, mnesia|odbc}
-
-Specify the backend used to store the tables: rosteritem and rostergroup.
-The default value is mnesia.
-If configured to odbc, then you must also configure in ejabberd
-the database connection (see the subsections of 3.2).
-
-
- {iqdisc, Discipline}
- This specifies
-the processing discipline for Roster Management (jabber:iq:roster) IQ queries (see section 3.3.2).
-
- access
-
-This option can be configured to specify rules to restrict roster management.
-If a rule returns ‘deny’ on the requested user name,
-that user cannot modify his personal roster:
-not add/remove/modify contacts,
-or subscribe/unsubscribe presence.
-By default there aren’t restrictions.
-
- {versioning, false|true}
- Enables
-Roster Versioning.
-This option is disabled by default.
-
- {store_current_id, false|true}
-
-If this option is enabled, the current version number is stored on the database.
-If disabled, the version number is calculated on the fly each time.
-Enabling this option reduces the load for both ejabberd and the database.
-This option does not affect the client in any way.
-This option is only useful if Roster Versioning is enabled.
-This option is disabled by default.
-Important: if you use mod_shared_roster, you must disable this option.
-
This example configuration enables Roster Versioning with storage of current id:
-
{modules,
- [
- ...
- {mod_roster, [{versioning, true}, {store_current_id, true}]},
- ...
- ]}.
-With this example configuration only admins can manage their rosters;
-everybody else cannot modify the roster:
-
{acl, admin, {user, "bob", "example.org"}}.
-{acl, admin, {user, "sarah", "example.org"}}.
-
-{access, roster, [{allow, admin},
- {deny, all}]}.
-
-{modules,
- [
- ...
- {mod_roster, [{access, roster}]},
- ...
- ]}.
-
-
-
This module adds support for logging end user packets via a XMPP message
-auditing service such as
-Bandersnatch. All user
-packets are encapsulated in a <route/> element and sent to the specified
-service(s).
Options:
-
-
-{loggers, [Names, ...]}
- With this option a (list of) service(s)
-that will receive the packets can be specified.
-
Examples:
-
-
-To log all end user packets to the Bandersnatch service running on
-bandersnatch.example.com:
-
{modules,
- [
- ...
- {mod_service_log, [{loggers, ["bandersnatch.example.com"]}]},
- ...
- ]}.
- - To log all end user packets to the Bandersnatch service running on
-bandersnatch.example.com and the backup service on
-bandersnatch.example.org:
-
{modules,
- [
- ...
- {mod_service_log, [{loggers, ["bandersnatch.example.com",
- "bandersnatch.example.org"]}]},
- ...
- ]}.
-
-
-
This module enables you to create shared roster groups. This means that you can
-create groups of people that can see members from (other) groups in their
-rosters. The big advantages of this feature are that end users do not need to
-manually add all users to their rosters, and that they cannot permanently delete
-users from the shared roster groups.
-A shared roster group can have members from any XMPP server,
-but the presence will only be available from and to members
-of the same virtual host where the group is created.
Shared roster groups can be edited only via the Web Admin. Each group
-has a unique identification and the following parameters:
-
-
-Name
- The name of the group, which will be displayed in the roster.
-
- Description
- The description of the group. This parameter does not affect
-anything.
-
- Members
- A list of full JIDs of group members, entered one per line in
-the Web Admin.
-To put as members all the registered users in the virtual hosts,
-you can use the special directive: @all@.
-Note that this directive is designed for a small server with just a few hundred users.
-
- Displayed groups
- A list of groups that will be in the rosters of this
-group’s members.
-
Examples:
-
-
-Take the case of a computer club that wants all its members seeing each
-other in their rosters. To achieve this, they need to create a shared roster
-group similar to next table:
-
-
| Identification | Group ‘club_members’ |
-| Name | Club Members |
-| Description | Members from the computer club |
-| Members | | member1@example.org |
-| member2@example.org |
-| member3@example.org |
-
|
-| Displayed groups | club_members |
-
-
- - In another case we have a company which has three divisions: Management,
-Marketing and Sales. All group members should see all other members in their
-rosters. Additionally, all managers should have all marketing and sales people
-in their roster. Simultaneously, all marketeers and the whole sales team
-should see all managers. This scenario can be achieved by creating shared
-roster groups as shown in the following table:
-
-
| Identification | Group ‘management’ | Group ‘marketing’ | Group ‘sales’ |
-| Name | Management | Marketing | Sales |
-| Description | |
-| Members | | manager1@example.org |
-| manager2@example.org |
-| manager3@example.org |
-| manager4@example.org |
-
- | | marketeer1@example.org |
-| marketeer2@example.org |
-| marketeer3@example.org |
-| marketeer4@example.org |
-
- | | saleswoman1@example.org |
-| salesman1@example.org |
-| saleswoman2@example.org |
-| salesman2@example.org |
-
|
-| Displayed groups | | management |
-| marketing |
-| sales |
-
- |
- | |
-
-
-
-
-
This module adds support for Server IP Check (XEP-0279). This protocol
-enables a client to discover its external IP address.
Options:
-
-
-{iqdisc, Discipline}
- This specifies
-the processing discipline for urn:xmpp:sic:0 IQ queries (see section 3.3.2).
-
-
-
This module adds support for Statistics Gathering (XEP-0039). This protocol
-allows you to retrieve next statistics from your ejabberd deployment:
-
-
-Total number of registered users on the current virtual host (users/total).
-
- Total number of registered users on all virtual hosts (users/all-hosts/total).
-
- Total number of online users on the current virtual host (users/online).
-
- Total number of online users on all virtual hosts (users/all-hosts/online).
-
Options:
-
-
-{iqdisc, Discipline}
- This specifies
-the processing discipline for Statistics Gathering (http://jabber.org/protocol/stats) IQ queries (see section 3.3.2).
-
As there are only a small amount of clients (for example
-Tkabber) and software libraries with
-support for this XEP, a few examples are given of the XML you need to send
-in order to get the statistics. Here they are:
-
-
-You can request the number of online users on the current virtual host
-(example.org) by sending:
-
<iq to='example.org' type='get'>
- <query xmlns='http://jabber.org/protocol/stats'>
- <stat name='users/online'/>
- </query>
-</iq>
-
- You can request the total number of registered users on all virtual hosts
-by sending:
-
<iq to='example.org' type='get'>
- <query xmlns='http://jabber.org/protocol/stats'>
- <stat name='users/all-hosts/total'/>
- </query>
-</iq>
-
-
-
This module features support for Entity Time (XEP-0202). By using this XEP,
-you are able to discover the time at another entity’s location.
Options:
-
-
-{iqdisc, Discipline}
- This specifies
-the processing discipline for Entity Time (jabber:iq:time) IQ queries (see section 3.3.2).
-
-
-
This module allows end users to store and retrieve their vCard, and to retrieve
-other users vCards, as defined in vcard-temp (XEP-0054). The module also
-implements an uncomplicated Jabber User Directory based on the vCards of
-these users. Moreover, it enables the server to send its vCard when queried.
Options:
-
-
-{backend, mnesia|odbc}
-
-Specify the backend used to store the tables: vcard.
-The default value is mnesia.
-If configured to odbc, then you must also configure in ejabberd
-the database connection (see the subsections of 3.2).
-
-
-
- {host, HostName}
- This option defines the Jabber ID of the
-service. If the host option is not specified, the Jabber ID will be the
-hostname of the virtual host with the prefix ‘vjud.’. The keyword "@HOST@"
-is replaced at start time with the real virtual host name.
-
-
- {iqdisc, Discipline}
- This specifies
-the processing discipline for vcard-temp IQ queries (see section 3.3.2).
-
- {search, true|false}
- This option specifies whether the search
-functionality is enabled or not
-If disabled, the option host will be ignored and the
-Jabber User Directory service will not appear in the Service Discovery item
-list. The default value is true.
-
- {matches, infinity|Number}
- With this option, the number of reported
-search results can be limited. If the option’s value is set to infinity,
-all search results are reported. The default value is 30.
-
- {allow_return_all, false|true}
- This option enables
-you to specify if search operations with empty input fields should return all
-users who added some information to their vCard. The default value is
-false.
-
- {search_all_hosts, true|false}
- If this option is set
-to true, search operations will apply to all virtual hosts. Otherwise
-only the current host will be searched. The default value is true.
-
Examples:
-
-
-In this first situation, search results are limited to twenty items,
-every user who added information to their vCard will be listed when people
-do an empty search, and only users from the current host will be returned:
-
{modules,
- [
- ...
- {mod_vcard, [{search, true},
- {matches, 20},
- {allow_return_all, true},
- {search_all_hosts, false}]},
- ...
- ]}.
- - The second situation differs in a way that search results are not limited,
-and that all virtual hosts will be searched instead of only the current one:
-
{modules,
- [
- ...
- {mod_vcard, [{search, true},
- {matches, infinity},
- {allow_return_all, true}]},
- ...
- ]}.
-
-
-
ejabberd can map LDAP attributes to vCard fields. This behaviour is
-implemented in the mod_vcard_ldap module. This module does not depend on the
-authentication method (see 3.2.5).
Usually ejabberd treats LDAP as a read-only storage:
-it is possible to consult data, but not possible to
-create accounts or edit vCard that is stored in LDAP.
-However, it is possible to change passwords if mod_register module is enabled
-and LDAP server supports
-RFC 3062.
The mod_vcard_ldap module has
-its own optional parameters. The first group of parameters has the same
-meaning as the top-level LDAP parameters to set the authentication method:
-ldap_servers, ldap_port, ldap_rootdn,
-ldap_password, ldap_base, ldap_uids, and
-ldap_filter. See section 3.2.5 for detailed information
-about these options. If one of these options is not set, ejabberd will look
-for the top-level option with the same name.
The second group of parameters
-consists of the following mod_vcard_ldap-specific options:
-
-
-{host, HostName}
- This option defines the Jabber ID of the
-service. If the host option is not specified, the Jabber ID will be the
-hostname of the virtual host with the prefix ‘vjud.’. The keyword "@HOST@"
-is replaced at start time with the real virtual host name.
-
-
- {iqdisc, Discipline}
- This specifies
-the processing discipline for vcard-temp IQ queries (see section 3.3.2).
-
- {search, true|false}
- This option specifies whether the search
-functionality is enabled (value: true) or disabled (value:
-false). If disabled, the option host will be ignored and the
-Jabber User Directory service will not appear in the Service Discovery item
-list. The default value is true.
-
- {matches, infinity|Number}
- With this option, the number of reported
-search results can be limited. If the option’s value is set to infinity,
-all search results are reported. The default value is 30.
-
- {ldap_vcard_map, [ {Name, Pattern, LDAPattributes}, ...]}
-
-With this option you can set the table that maps LDAP attributes to vCard fields.
-
-Name is the type name of the vCard as defined in
-RFC 2426.
-Pattern is a string which contains pattern variables
-"%u", "%d" or "%s".
-LDAPattributes is the list containing LDAP attributes.
-The pattern variables
-"%s" will be sequentially replaced
-with the values of LDAP attributes from List_of_LDAP_attributes,
-"%u" will be replaced with the user part of a JID,
-and "%d" will be replaced with the domain part of a JID.
-The default is:
-
[{"NICKNAME", "%u", []},
- {"FN", "%s", ["displayName"]},
- {"LAST", "%s", ["sn"]},
- {"FIRST", "%s", ["givenName"]},
- {"MIDDLE", "%s", ["initials"]},
- {"ORGNAME", "%s", ["o"]},
- {"ORGUNIT", "%s", ["ou"]},
- {"CTRY", "%s", ["c"]},
- {"LOCALITY", "%s", ["l"]},
- {"STREET", "%s", ["street"]},
- {"REGION", "%s", ["st"]},
- {"PCODE", "%s", ["postalCode"]},
- {"TITLE", "%s", ["title"]},
- {"URL", "%s", ["labeleduri"]},
- {"DESC", "%s", ["description"]},
- {"TEL", "%s", ["telephoneNumber"]},
- {"EMAIL", "%s", ["mail"]},
- {"BDAY", "%s", ["birthDay"]},
- {"ROLE", "%s", ["employeeType"]},
- {"PHOTO", "%s", ["jpegPhoto"]}]
- - {ldap_search_fields, [ {Name, Attribute}, ...]}
- This option
-defines the search form and the LDAP attributes to search within.
-Name is the name of a search form
-field which will be automatically translated by using the translation
-files (see msgs/*.msg for available words). Attribute is the
-LDAP attribute or the pattern "%u". The default is:
-
[{"User", "%u"},
- {"Full Name", "displayName"},
- {"Given Name", "givenName"},
- {"Middle Name", "initials"},
- {"Family Name", "sn"},
- {"Nickname", "%u"},
- {"Birthday", "birthDay"},
- {"Country", "c"},
- {"City", "l"},
- {"Email", "mail"},
- {"Organization Name", "o"},
- {"Organization Unit", "ou"}]
- - {ldap_search_reported, [ {SearchField, VcardField}, ...]}
- This option
-defines which search fields should be reported.
-SearchField is the name of a search form
-field which will be automatically translated by using the translation
-files (see msgs/*.msg for available words). VcardField is the
-vCard field name defined in the ldap_vcard_map option. The default
-is:
-
[{"Full Name", "FN"},
- {"Given Name", "FIRST"},
- {"Middle Name", "MIDDLE"},
- {"Family Name", "LAST"},
- {"Nickname", "NICKNAME"},
- {"Birthday", "BDAY"},
- {"Country", "CTRY"},
- {"City", "LOCALITY"},
- {"Email", "EMAIL"},
- {"Organization Name", "ORGNAME"},
- {"Organization Unit", "ORGUNIT"}]
-
Examples:
-
-
-
Let’s say ldap.example.org is the name of our LDAP server. We have
-users with their passwords in "ou=Users,dc=example,dc=org" directory.
-Also we have addressbook, which contains users emails and their additional
-infos in "ou=AddressBook,dc=example,dc=org" directory. Corresponding
-authentication section should looks like this:
%% authentication method
-{auth_method, ldap}.
-%% DNS name of our LDAP server
-{ldap_servers, ["ldap.example.org"]}.
-%% We want to authorize users from 'shadowAccount' object class only
-{ldap_filter, "(objectClass=shadowAccount)"}.
-Now we want to use users LDAP-info as their vCards. We have four attributes
-defined in our LDAP schema: "mail" — email address, "givenName"
-— first name, "sn" — second name, "birthDay" — birthday.
-Also we want users to search each other. Let’s see how we can set it up:
{modules,
- ...
- {mod_vcard_ldap,
- [
- %% We use the same server and port, but want to bind anonymously because
- %% our LDAP server accepts anonymous requests to
- %% "ou=AddressBook,dc=example,dc=org" subtree.
- {ldap_rootdn, ""},
- {ldap_password, ""},
- %% define the addressbook's base
- {ldap_base, "ou=AddressBook,dc=example,dc=org"},
- %% uidattr: user's part of JID is located in the "mail" attribute
- %% uidattr_format: common format for our emails
- {ldap_uids, [{"mail","%u@mail.example.org"}]},
- %% We have to define empty filter here, because entries in addressbook does not
- %% belong to shadowAccount object class
- {ldap_filter, ""},
- %% Now we want to define vCard pattern
- {ldap_vcard_map,
- [{"NICKNAME", "%u", []}, % just use user's part of JID as his nickname
- {"FIRST", "%s", ["givenName"]},
- {"LAST", "%s", ["sn"]},
- {"FN", "%s, %s", ["sn", "givenName"]}, % example: "Smith, John"
- {"EMAIL", "%s", ["mail"]},
- {"BDAY", "%s", ["birthDay"]}]},
- %% Search form
- {ldap_search_fields,
- [{"User", "%u"},
- {"Name", "givenName"},
- {"Family Name", "sn"},
- {"Email", "mail"},
- {"Birthday", "birthDay"}]},
- %% vCard fields to be reported
- %% Note that JID is always returned with search results
- {ldap_search_reported,
- [{"Full Name", "FN"},
- {"Nickname", "NICKNAME"},
- {"Birthday", "BDAY"}]}
- ]}
- ...
-}.
-Note that mod_vcard_ldap module checks an existence of the user before
-searching his info in LDAP.
- ldap_vcard_map example:
-
{ldap_vcard_map,
- [{"NICKNAME", "%u", []},
- {"FN", "%s", ["displayName"]},
- {"CTRY", "Russia", []},
- {"EMAIL", "%u@%d", []},
- {"DESC", "%s\n%s", ["title", "description"]}
- ]},
- - ldap_search_fields example:
-
{ldap_search_fields,
- [{"User", "uid"},
- {"Full Name", "displayName"},
- {"Email", "mail"}
- ]},
- - ldap_search_reported example:
-
{ldap_search_reported,
- [{"Full Name", "FN"},
- {"Email", "EMAIL"},
- {"Birthday", "BDAY"},
- {"Nickname", "NICKNAME"}
- ]},
-
-
-
The user’s client can store an avatar in the user vCard.
-The vCard-Based Avatars protocol (XEP-0153)
-provides a method for clients to inform the contacts what is the avatar hash value.
-However, simple or small clients may not implement that protocol.
If this module is enabled, all the outgoing client presence stanzas get automatically
-the avatar hash on behalf of the client.
-So, the contacts receive the presence stanzas with the Update Data described
-in XEP-0153 as if the client would had inserted it itself.
-If the client had already included such element in the presence stanza,
-it is replaced with the element generated by ejabberd.
By enabling this module, each vCard modification produces a hash recalculation,
-and each presence sent by a client produces hash retrieval and a
-presence stanza rewrite.
-For this reason, enabling this module will introduce a computational overhead
-in servers with clients that change frequently their presence.
-
-
This module implements Software Version (XEP-0092). Consequently, it
-answers ejabberd’s version when queried.
Options:
-
-
-{show_os, true|false}
- Should the operating system be revealed or not.
-The default value is true.
-
- {iqdisc, Discipline}
- This specifies
-the processing discipline for Software Version (jabber:iq:version) IQ queries (see section 3.3.2).
-
-
-
With the ejabberdctl command line administration script
-you can execute ejabberdctl commands (described in the next section, 4.1.1)
-and also many general ejabberd commands (described in section 4.2).
-This means you can start, stop and perform many other administrative tasks
-in a local or remote ejabberd server (by providing the argument --node NODENAME).
The ejabberdctl script can be configured in the file ejabberdctl.cfg.
-This file includes detailed information about each configurable option. See section 4.1.2.
The ejabberdctl script returns a numerical status code.
-Success is represented by 0,
-error is represented by 1,
-and other codes may be used for specific results.
-This can be used by other scripts to determine automatically
-if a command succeeded or failed,
-for example using: echo $?
-
When ejabberdctl is executed without any parameter,
-it displays the available options. If there isn’t an ejabberd server running,
-the available parameters are:
-
-
-start
- Start ejabberd in background mode. This is the default method.
-
- debug
- Attach an Erlang shell to an already existing ejabberd server. This allows to execute commands interactively in the ejabberd server.
-
- live
- Start ejabberd in live mode: the shell keeps attached to the started server, showing log messages and allowing to execute interactive commands.
-
If there is an ejabberd server running in the system,
-ejabberdctl shows the ejabberdctl commands described bellow
-and all the ejabberd commands available in that server (see 4.2.1).
The ejabberdctl commands are:
-
-
-help
- Get help about ejabberdctl or any available command. Try ejabberdctl help help.
-
- status
- Check the status of the ejabberd server.
-
- stop
- Stop the ejabberd server.
-
- restart
- Restart the ejabberd server.
-
- mnesia
- Get information about the Mnesia database.
-
The ejabberdctl script can be restricted to require authentication
-and execute some ejabberd commands; see 4.2.2.
-Add the option to the file ejabberd.cfg.
-In this example there is no restriction:
-
{ejabberdctl_access_commands, []}.
-If account robot1@example.org is registered in ejabberd with password abcdef
-(which MD5 is E8B501798950FC58AAD83C8C14978E),
-and ejabberd.cfg contains this setting:
-
{hosts, ["example.org"]}.
-{acl, bots, {user, "robot1", "example.org"}}.
-{access, ctlaccess, [{allow, bots}]}.
-{ejabberdctl_access_commands, [ {ctlaccess, [registered_users, register], []} ]}.
-then you can do this in the shell:
-
$ ejabberdctl registered_users example.org
-Error: no_auth_provided
-$ ejabberdctl --auth robot1 example.org E8B501798950FC58AAD83C8C14978E registered_users example.org
-robot1
-testuser1
-testuser2
-
-
ejabberd is an Erlang/OTP application that runs inside an Erlang runtime system.
-This system is configured using environment variables and command line parameters.
-The ejabberdctl administration script uses many of those possibilities.
-You can configure some of them with the file ejabberdctl.cfg,
-which includes detailed description about them.
-This section describes for reference purposes
-all the environment variables and command line parameters.
The environment variables:
-
-
-EJABBERD_CONFIG_PATH
-
- Path to the ejabberd configuration file.
-
- EJABBERD_MSGS_PATH
-
- Path to the directory with translated strings.
-
- EJABBERD_LOG_PATH
-
- Path to the ejabberd service log file.
-
- EJABBERD_SO_PATH
-
- Path to the directory with binary system libraries.
-
- EJABBERD_DOC_PATH
-
- Path to the directory with ejabberd documentation.
-
- EJABBERD_PID_PATH
-
- Path to the PID file that ejabberd can create when started.
-
- HOME
-
- Path to the directory that is considered ejabberd’s home.
- This path is used to read the file .erlang.cookie.
-
- ERL_CRASH_DUMP
-
- Path to the file where crash reports will be dumped.
-
- ERL_INETRC
-
- Indicates which IP name resolution to use.
- If using -sname, specify either this option or -kernel inetrc filepath.
-
- ERL_MAX_PORTS
-
- Maximum number of simultaneously open Erlang ports.
-
- ERL_MAX_ETS_TABLES
-
- Maximum number of ETS and Mnesia tables.
-
The command line parameters:
-
-
--sname ejabberd
-
- The Erlang node will be identified using only the first part
- of the host name, i. e. other Erlang nodes outside this domain cannot contact
- this node. This is the preferable option in most cases.
-
- -name ejabberd
-
- The Erlang node will be fully identified.
-This is only useful if you plan to setup an ejabberd cluster with nodes in different networks.
-
- -kernel inetrc ’"/etc/ejabberd/inetrc"’
-
- Indicates which IP name resolution to use.
- If using -sname, specify either this option or ERL_INETRC.
-
- -kernel inet_dist_listen_min 4200 inet_dist_listen_min 4210
-
- Define the first and last ports that epmd (section 5.2) can listen to.
-
- -detached
-
-Starts the Erlang system detached from the system console.
- Useful for running daemons and backgrounds processes.
-
- -noinput
-
- Ensures that the Erlang system never tries to read any input.
- Useful for running daemons and backgrounds processes.
-
- -pa /var/lib/ejabberd/ebin
-
- Specify the directory where Erlang binary files (*.beam) are located.
-
- -s ejabberd
-
- Tell Erlang runtime system to start the ejabberd application.
-
- -mnesia dir ’"/var/lib/ejabberd/"’
-
- Specify the Mnesia database directory.
-
- -sasl sasl_error_logger {file, "/var/log/ejabberd/erlang.log"}
-
- Path to the Erlang/OTP system log file.
-SASL here means “System Architecture Support Libraries”
-not “Simple Authentication and Security Layer”.
-
- +K [true|false]
-
- Kernel polling.
-
- -smp [auto|enable|disable]
-
- SMP support.
-
- +P 250000
-
- Maximum number of Erlang processes.
-
- -remsh ejabberd@localhost
-
- Open an Erlang shell in a remote Erlang node.
-
- -hidden
-
- The connections to other nodes are hidden (not published).
- The result is that this node is not considered part of the cluster.
- This is important when starting a temporary ctl or debug node.
-
-Note that some characters need to be escaped when used in shell scripts, for instance " and {}.
-You can find other options in the Erlang manual page (erl -man erl).
-
An ejabberd command is an abstract function identified by a name,
-with a defined number and type of calling arguments and type of result
-that is registered in the ejabberd_commands service.
-Those commands can be defined in any Erlang module and executed using any valid frontend.
ejabberd includes a frontend to execute ejabberd commands: the script ejabberdctl.
-Other known frontends that can be installed to execute ejabberd commands in different ways are:
-ejabberd_xmlrpc (XML-RPC service),
-mod_rest (HTTP POST service),
-mod_shcommands (ejabberd WebAdmin page).
-
ejabberd includes a few ejabberd Commands by default.
-When more modules are installed, new commands may be available in the frontends.
The easiest way to get a list of the available commands, and get help for them is to use
-the ejabberdctl script:
-
$ ejabberdctl help
-Usage: ejabberdctl [--node nodename] [--auth user host password] command [options]
-
-Available commands in this ejabberd node:
- backup file Store the database to backup file
- connected_users List all established sessions
- connected_users_number Get the number of established sessions
- ...
-
The most interesting ones are:
-
-
-reopen_log
- Reopen the log files after they were renamed.
-If the old files were not renamed before calling this command,
-they are automatically renamed to "*-old.log". See section 7.1.
-
- backup ejabberd.backup
-
-Store internal Mnesia database to a binary backup file.
-
- restore ejabberd.backup
-
-Restore immediately from a binary backup file the internal Mnesia database.
-This will consume a lot of memory if you have a large database,
-so better use install_fallback.
-
- install_fallback ejabberd.backup
-
-The binary backup file is installed as fallback:
-it will be used to restore the database at the next ejabberd start.
-This means that, after running this command, you have to restart ejabberd.
-This command requires less memory than restore.
-
- dump ejabberd.dump
-
-Dump internal Mnesia database to a text file dump.
-
- load ejabberd.dump
-
-Restore immediately from a text file dump.
-This is not recommended for big databases, as it will consume much time,
-memory and processor. In that case it’s preferable to use backup and install_fallback.
-
- import_piefxis, export_piefxis, export_piefxis_host
-
-These options can be used to migrate accounts
-using XEP-0227 formatted XML files
-from/to other Jabber/XMPP servers
-or move users of a vhost to another ejabberd installation.
-See also ejabberd migration kit.
-
- import_file, import_dir
-
-These options can be used to migrate accounts
-using jabberd1.4 formatted XML files.
-from other Jabber/XMPP servers
-There exist tutorials to
-migrate from other software to ejabberd.
-
- delete_expired_messages
- This option can be used to delete old messages
-in offline storage. This might be useful when the number of offline messages
-is very high.
-
- delete_old_messages days
- Delete offline messages older than the given days.
-
- register user host password
- Register an account in that domain with the given password.
-
- unregister user host
- Unregister the given account.
-
-
The frontends can be configured to restrict access to certain commands.
-In that case, authentication information must be provided.
-In each frontend the AccessCommands option is defined
-in a different place. But in all cases the option syntax is the same:
-
AccessCommands = [ {Access, CommandNames, Arguments}, ...]
-Access = atom()
-CommandNames = all | [CommandName]
-CommandName = atom()
-Arguments = [ {ArgumentName, ArgumentValue}, ...]
-ArgumentName = atom()
-ArgumentValue = any()
-The default value is to not define any restriction: [].
-The authentication information is provided when executing a command,
-and is Username, Hostname and Password of a local XMPP account
-that has permission to execute the corresponding command.
-This means that the account must be registered in the local ejabberd,
-because the information will be verified.
-It is possible to provide the plaintext password or its MD5 sum.
When one or several access restrictions are defined and the
-authentication information is provided,
-each restriction is verified until one matches completely:
-the account matches the Access rule,
-the command name is listed in CommandNames,
-and the provided arguments do not contradict Arguments.
As an example to understand the syntax, let’s suppose those options:
-
{hosts, ["example.org"]}.
-{acl, bots, {user, "robot1", "example.org"}}.
-{access, commaccess, [{allow, bots}]}.
-This list of access restrictions allows only robot1@example.org to execute all commands:
-
[{commaccess, all, []}]
-See another list of restrictions (the corresponding ACL and ACCESS are not shown):
-
[
- %% This bot can execute all commands:
- {bot, all, []},
- %% This bot can only execute the command 'dump'. No argument restriction:
- {bot_backups, [dump], []}
- %% This bot can execute all commands,
- %% but if a 'host' argument is provided, it must be "example.org":
- {bot_all_example, all, [{host, "example.org"}]},
- %% This bot can only execute the command 'register',
- %% and if argument 'host' is provided, it must be "example.org":
- {bot_reg_example, [register], [{host, "example.org"}]},
- %% This bot can execute the commands 'register' and 'unregister',
- %% if argument host is provided, it must be "test.org":
- {_bot_reg_test, [register, unregister], [{host, "test.org"}]}
-]
-
-
-
The ejabberd Web Admin allows to administer most of ejabberd using a web browser.
This feature is enabled by default:
-a ejabberd_http listener with the option web_admin (see
-section 3.1.3) is included in the listening ports. Then you can open
-http://server:port/admin/ in your favourite web browser. You
-will be asked to enter the username (the full Jabber ID) and password
-of an ejabberd user with administrator rights. After authentication
-you will see a page similar to figure 4.1.
-
-
-
-
-
| Figure 4.1: Top page from the Web Admin |
-
-
-
-Here you can edit access restrictions, manage users, create backups,
-manage the database, enable/disable ports listened for, view server
-statistics,…
The access rule configure determines what accounts can access the Web Admin and modify it.
-The access rule webadmin_view is to grant only view access: those accounts can browse the Web Admin with read-only access.
Example configurations:
-
-
-You can serve the Web Admin on the same port as the
-HTTP Polling interface. In this example
-you should point your web browser to
http://example.org:5280/admin/ to
-administer all virtual hosts or to
-http://example.org:5280/admin/server/example.com/ to administer only
-the virtual host example.com. Before you get access to the Web Admin
-you need to enter as username, the JID and password from a registered user
-that is allowed to configure ejabberd. In this example you can enter as
-username ‘admin@example.net’ to administer all virtual hosts (first
-URL). If you log in with ‘admin@example.com’ on
- http://example.org:5280/admin/server/example.com/ you can only
-administer the virtual host example.com.
-The account ‘reviewer@example.com’ can browse that vhost in read-only mode.
-{acl, admins, {user, "admin", "example.net"}}.
-{host_config, "example.com", [{acl, admins, {user, "admin", "example.com"}}]}.
-{host_config, "example.com", [{acl, viewers, {user, "reviewer", "example.com"}}]}.
-
-{access, configure, [{allow, admins}]}.
-{access, webadmin_view, [{allow, viewers}]}.
-
-{hosts, ["example.org"]}.
-
-{listen,
- [
- ...
- {5280, ejabberd_http, [http_poll, web_admin]},
- ...
- ]}.
- - For security reasons, you can serve the Web Admin on a secured
-connection, on a port differing from the HTTP Polling interface, and bind it
-to the internal LAN IP. The Web Admin will be accessible by pointing your
-web browser to
https://192.168.1.1:5282/admin/:
-
-{hosts, ["example.org"]}.
-
-{listen,
- [
- ...
- {5280, ejabberd_http, [
- http_poll
- ]},
- {{5282, "192.168.1.1"}, ejabberd_http, [
- web_admin,
- tls, {certfile, "/usr/local/etc/server.pem"}
- ]},
- ...
- ]}.
-
Certain pages in the ejabberd Web Admin contain a link to a related
-section in the ejabberd Installation and Operation Guide.
-In order to view such links, a copy in HTML format of the Guide must
-be installed in the system.
-The file is searched by default in
-"/share/doc/ejabberd/guide.html".
-The directory of the documentation can be specified in
-the environment variable EJABBERD_DOC_PATH.
-See section 4.1.2.
-
If you enable mod_configure and mod_adhoc,
-you can perform several administrative tasks in ejabberd
-with a XMPP client.
-The client must support Ad-Hoc Commands (XEP-0050),
-and you must login in the XMPP server with
-an account with proper privileges.
-
ejabberd uses the distributed Mnesia database.
-Being distributed, Mnesia enforces consistency of its file,
-so it stores the name of the Erlang node in it (see section 5.4).
-The name of an Erlang node includes the hostname of the computer.
-So, the name of the Erlang node changes
-if you change the name of the machine in which ejabberd runs,
-or when you move ejabberd to a different machine.
You have two ways to use the old Mnesia database in an ejabberd with new node name:
-put the old node name in ejabberdctl.cfg,
-or convert the database to the new node name.
Those example steps will backup, convert and load the Mnesia database.
-You need to have either the old Mnesia spool dir or a backup of Mnesia.
-If you already have a backup file of the old database, you can go directly to step 5.
-You also need to know the old node name and the new node name.
-If you don’t know them, look for them by executing ejabberdctl
-or in the ejabberd log files.
Before starting, setup some variables:
-
OLDNODE=ejabberd@oldmachine
-NEWNODE=ejabberd@newmachine
-OLDFILE=/tmp/old.backup
-NEWFILE=/tmp/new.backup
-
-
-Start ejabberd enforcing the old node name:
-
ejabberdctl --node $OLDNODE start
-
- Generate a backup file:
-
ejabberdctl --node $OLDNODE backup $OLDFILE
-
- Stop the old node:
-
ejabberdctl --node $OLDNODE stop
-
- Make sure there aren’t files in the Mnesia spool dir. For example:
-
mkdir /var/lib/ejabberd/oldfiles
-mv /var/lib/ejabberd/*.* /var/lib/ejabberd/oldfiles/
-
- Start ejabberd. There isn’t any need to specify the node name anymore:
-
ejabberdctl start
-
- Convert the backup to new node name:
-
ejabberdctl mnesia_change_nodename $OLDNODE $NEWNODE $OLDFILE $NEWFILE
-
- Install the backup file as a fallback:
-
ejabberdctl install_fallback $NEWFILE
-
- Stop ejabberd:
-
ejabberdctl stop
-
You may see an error message in the log files, it’s normal, so don’t worry:
-Mnesia(ejabberd@newmachine):
-** ERROR ** (ignoring core)
-** FATAL ** A fallback is installed and Mnesia must be restarted.
- Forcing shutdown after mnesia_down from ejabberd@newmachine...
-
- Now you can finally start ejabberd:
-
ejabberdctl start
-
- Check that the information of the old database is available: accounts, rosters...
-After you finish, remember to delete the temporary backup files from public directories.
-
-
-
-
You need to take the following TCP ports in mind when configuring your firewall:
-
-
| Port | Description |
-| 5222 | Standard port for Jabber/XMPP client connections, plain or STARTTLS. |
-| 5223 | Standard port for Jabber client connections using the old SSL method. |
-| 5269 | Standard port for Jabber/XMPP server connections. |
-| 4369 | EPMD (section 5.2) listens for Erlang node name requests. |
-| port range | Used for connections between Erlang nodes. This range is configurable (see section 5.2). |
-
-
-
epmd (Erlang Port Mapper Daemon)
-is a small name server included in Erlang/OTP
-and used by Erlang programs when establishing distributed Erlang communications.
-ejabberd needs epmd to use ejabberdctl and also when clustering ejabberd nodes.
-This small program is automatically started by Erlang, and is never stopped.
-If ejabberd is stopped, and there aren’t any other Erlang programs
-running in the system, you can safely stop epmd if you want.
ejabberd runs inside an Erlang node.
-To communicate with ejabberd, the script ejabberdctl starts a new Erlang node
-and connects to the Erlang node that holds ejabberd.
-In order for this communication to work,
-epmd must be running and listening for name requests in the port 4369.
-You should block the port 4369 in the firewall in such a way that
-only the programs in your machine can access it.
If you build a cluster of several ejabberd instances,
-each ejabberd instance is called an ejabberd node.
-Those ejabberd nodes use a special Erlang communication method to
-build the cluster, and EPMD is again needed listening in the port 4369.
-So, if you plan to build a cluster of ejabberd nodes
-you must open the port 4369 for the machines involved in the cluster.
-Remember to block the port so Internet doesn’t have access to it.
Once an Erlang node solved the node name of another Erlang node using EPMD and port 4369,
-the nodes communicate directly.
-The ports used in this case by default are random,
-but can be configured in the file ejabberdctl.cfg.
-The Erlang command-line parameter used internally is, for example:
-
erl ... -kernel inet_dist_listen_min 4370 inet_dist_listen_max 4375
-
-
The Erlang cookie is a string with numbers and letters.
-An Erlang node reads the cookie at startup from the command-line parameter -setcookie.
-If not indicated, the cookie is read from the cookie file $HOME/.erlang.cookie.
-If this file does not exist, it is created immediately with a random cookie.
-Two Erlang nodes communicate only if they have the same cookie.
-Setting a cookie on the Erlang node allows you to structure your Erlang network
-and define which nodes are allowed to connect to which.
Thanks to Erlang cookies, you can prevent access to the Erlang node by mistake,
-for example when there are several Erlang nodes running different programs in the same machine.
Setting a secret cookie is a simple method
-to difficult unauthorized access to your Erlang node.
-However, the cookie system is not ultimately effective
-to prevent unauthorized access or intrusion to an Erlang node.
-The communication between Erlang nodes are not encrypted,
-so the cookie could be read sniffing the traffic on the network.
-The recommended way to secure the Erlang node is to block the port 4369.
-
An Erlang node may have a node name.
-The name can be short (if indicated with the command-line parameter -sname)
-or long (if indicated with the parameter -name).
-Starting an Erlang node with -sname limits the communication between Erlang nodes to the LAN.
Using the option -sname instead of -name is a simple method
-to difficult unauthorized access to your Erlang node.
-However, it is not ultimately effective to prevent access to the Erlang node,
-because it may be possible to fake the fact that you are on another network
-using a modified version of Erlang epmd.
-The recommended way to secure the Erlang node is to block the port 4369.
-
ejabberd stores sensitive data in the file system either in plain text or binary files.
-The file system permissions should be set to only allow the proper user to read,
-write and execute those files and directories.
-
-ejabberd configuration file: /etc/ejabberd/ejabberd.cfg
-
-Contains the JID of administrators
-and passwords of external components.
-The backup files probably contain also this information,
-so it is preferable to secure the whole /etc/ejabberd/ directory.
-
- ejabberd service log: /var/log/ejabberd/ejabberd.log
-
-Contains IP addresses of clients.
-If the loglevel is set to 5, it contains whole conversations and passwords.
-If a logrotate system is used, there may be several log files with similar information,
-so it is preferable to secure the whole /var/log/ejabberd/ directory.
-
- Mnesia database spool files in /var/lib/ejabberd/
-
-The files store binary data, but some parts are still readable.
-The files are generated by Mnesia and their permissions cannot be set directly,
-so it is preferable to secure the whole /var/lib/ejabberd/ directory.
-
- Erlang cookie file: /var/lib/ejabberd/.erlang.cookie
-
-See section 5.3.
-
-
-
-
-
A XMPP domain is served by one or more ejabberd nodes. These nodes can
-be run on different machines that are connected via a network. They all
-must have the ability to connect to port 4369 of all another nodes, and must
-have the same magic cookie (see Erlang/OTP documentation, in other words the
-file ~ejabberd/.erlang.cookie must be the same on all nodes). This is
-needed because all nodes exchange information about connected users, s2s
-connections, registered services, etc…
Each ejabberd node has the following modules:
-
-
-router,
-
- local router,
-
- session manager,
-
- s2s manager.
-
-
-
This module is the main router of XMPP packets on each node. It
-routes them based on their destination’s domains. It uses a global
-routing table. The domain of the packet’s destination is searched in the
-routing table, and if it is found, the packet is routed to the
-appropriate process. If not, it is sent to the s2s manager.
-
-
This module routes packets which have a destination domain equal to
-one of this server’s host names. If the destination JID has a non-empty user
-part, it is routed to the session manager, otherwise it is processed depending
-on its content.
-
-
This module routes packets to local users. It looks up to which user
-resource a packet must be sent via a presence table. Then the packet is
-either routed to the appropriate c2s process, or stored in offline
-storage, or bounced back.
-
-
This module routes packets to other XMPP servers. First, it
-checks if an opened s2s connection from the domain of the packet’s
-source to the domain of the packet’s destination exists. If that is the case,
-the s2s manager routes the packet to the process
-serving this connection, otherwise a new connection is opened.
-
-
Suppose you already configured ejabberd on one machine named (first),
-and you need to setup another one to make an ejabberd cluster. Then do
-following steps:
-
-Copy
~ejabberd/.erlang.cookie file from first to
-second.(alt) You can also add ‘-setcookie content_of_.erlang.cookie’
-option to all ‘erl’ commands below.
- On second run the following command as the ejabberd daemon user,
-in the working directory of ejabberd:
erl -sname ejabberd \
- -mnesia dir '"/var/lib/ejabberd/"' \
- -mnesia extra_db_nodes "['ejabberd@first']" \
- -s mnesia
-
This will start Mnesia serving the same database as ejabberd@first.
-You can check this by running the command ‘mnesia:info().’. You
-should see a lot of remote tables and a line like the following:
Note: the Mnesia directory may be different in your system.
-To know where does ejabberd expect Mnesia to be installed by default,
-call 4.1 without options and it will show some help,
-including the Mnesia database spool dir.
running db nodes = [ejabberd@first, ejabberd@second]
-
- Now run the following in the same ‘erl’ session:
mnesia:change_table_copy_type(schema, node(), disc_copies).
-
This will create local disc storage for the database.
(alt) Change storage type of the scheme table to ‘RAM and disc
-copy’ on the second node via the Web Admin.
- Now you can add replicas of various tables to this node with
-‘
mnesia:add_table_copy’ or
-‘mnesia:change_table_copy_type’ as above (just replace
-‘schema’ with another table name and ‘disc_copies’
-can be replaced with ‘ram_copies’ or
-‘disc_only_copies’).Which tables to replicate is very dependant on your needs, you can get
-some hints from the command ‘mnesia:info().’, by looking at the
-size of tables and the default storage type for each table on ’first’.
Replicating a table makes lookups in this table faster on this node.
-Writing, on the other hand, will be slower. And of course if machine with one
-of the replicas is down, other replicas will be used.
Also section 5.3 (Table Fragmentation) of Mnesia User’s Guide can be helpful.
-
(alt) Same as in previous item, but for other tables.
- Run ‘
init:stop().’ or just ‘q().’ to exit from
-the Erlang shell. This probably can take some time if Mnesia has not yet
-transfered and processed all data it needed from first. - Now run ejabberd on second with a configuration similar as
-on first: you probably do not need to duplicate ‘
acl’
-and ‘access’ options because they will be taken from
-first. If you installed mod_irc, notice that it should be
-enabled only on one machine in the cluster.
-
You can repeat these steps for other machines supposed to serve this
-domain.
-
-
-
-
-
ejabberd includes an algorithm to load balance the components that are plugged on an ejabberd cluster. It means that you can plug one or several instances of the same component on each ejabberd cluster and that the traffic will be automatically distributed.
The default distribution algorithm try to deliver to a local instance of a component. If several local instances are available, one instance is chosen randomly. If no instance is available locally, one instance is chosen randomly among the remote component instances.
If you need a different behaviour, you can change the load balancing behaviour with the option domain_balancing. The syntax of the option is the following:
-
- {domain_balancing, "component.example.com", BalancingCriteria}.
Several balancing criteria are available:
-
-
-destination: the full JID of the packet to attribute is used.
-
- source: the full JID of the packet from attribute is used.
-
- bare_destination: the bare JID (without resource) of the packet to attribute is used.
-
- bare_source: the bare JID (without resource) of the packet from attribute is used.
-
If the value corresponding to the criteria is the same, the same component instance in the cluster will be used.
-
-
When there is a risk of failure for a given component, domain balancing can cause service trouble. If one component is failing the service will not work correctly unless the sessions are rebalanced.
In this case, it is best to limit the problem to the sessions handled by the failing component. This is what the domain_balancing_component_number option does, making the load balancing algorithm not dynamic, but sticky on a fix number of component instances.
The syntax is:
-
- {domain_balancing_component_number, "component.example.com", Number}.
-
-
-
An ejabberd node writes two log files:
-
-
- ejabberd.log
- is the ejabberd service log, with the messages reported by ejabberd code
-
- erlang.log
- is the Erlang/OTP system log, with the messages reported by Erlang/OTP using SASL (System Architecture Support Libraries)
-
The option loglevel modifies the verbosity of the file ejabberd.log. The syntax is:
-
- {loglevel, Level}.
The possible Level are:
-
-
- 0
- No ejabberd log at all (not recommended)
-
- 1
- Critical
-
- 2
- Error
-
- 3
- Warning
-
- 4
- Info
-
- 5
- Debug
-
-For example, the default configuration is:
-
{loglevel, 4}.
-The log files grow continually, so it is recommended to rotate them periodically.
-To rotate the log files, rename the files and then reopen them.
-The ejabberdctl command reopen-log
-(please refer to section 4.1.1)
-reopens the log files,
-and also renames the old ones if you didn’t rename them.
-
The Debug Console is an Erlang shell attached to an already running ejabberd server.
-With this Erlang shell, an experienced administrator can perform complex tasks.
This shell gives complete control over the ejabberd server,
-so it is important to use it with extremely care.
-There are some simple and safe examples in the article
-Interconnecting Erlang Nodes
To exit the shell, close the window or press the keys: control+c control+c.
-
-
ejabberd includes a watchdog mechanism that may be useful to developers
-when troubleshooting a problem related to memory usage.
-If a process in the ejabberd server consumes more memory than the configured threshold,
-a message is sent to the XMPP accounts defined with the option
-watchdog_admins
- in the ejabberd configuration file.
The syntax is:
-
- {watchdog_admins, [JID, ...]}.
The memory consumed is measured in words:
-a word on 32-bit architecture is 4 bytes,
-and a word on 64-bit architecture is 8 bytes.
-The threshold by default is 1000000 words.
-This value can be configured with the option watchdog_large_heap,
-or in a conversation with the watchdog alert bot.
The syntax is:
-
- {watchdog_large_heap, Number}.
Example configuration:
-
{watchdog_admins, ["admin2@localhost", "admin2@example.org"]}.
-{watchdog_large_heap, 30000000}.
-To remove watchdog admins, remove them in the option.
-To remove all watchdog admins, set the option with an empty list:
-
{watchdog_admins, []}.
-
-
-
The source code of ejabberd supports localization.
-The translators can edit the
-gettext .po files
-using any capable program (KBabel, Lokalize, Poedit...) or a simple text editor.
Then gettext
-is used to extract, update and export those .po files to the .msg format read by ejabberd.
-To perform those management tasks, in the src/ directory execute make translations.
-The translatable strings are extracted from source code to generate the file ejabberd.pot.
-This file is merged with each .po file to produce updated .po files.
-Finally those .po files are exported to .msg files, that have a format easily readable by ejabberd.
All built-in modules support the xml:lang attribute inside IQ queries.
-Figure A.1, for example, shows the reply to the following query:
-
<iq id='5'
- to='example.org'
- type='get'
- xml:lang='ru'>
- <query xmlns='http://jabber.org/protocol/disco#items'/>
-</iq>
-
-
-
-
-
-
| Figure A.1: Service Discovery when xml:lang=’ru’ |
-
-
-
The Web Admin also supports the Accept-Language HTTP header.
-
-
-
-
-
| Figure A.2: Web Admin showing a virtual host when the web browser provides the
-HTTP header ‘Accept-Language: ru’ |
-
-
-
-
-
Release notes are available from ejabberd Home Page
-
Thanks to all people who contributed to this guide:
-
-
Ejabberd Installation and Operation Guide.
-Copyright © 2003 — 2010 ProcessOne
This document is free software; you can redistribute it and/or
-modify it under the terms of the GNU General Public License
-as published by the Free Software Foundation; either version 2
-of the License, or (at your option) any later version.
This document is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with
-this document; if not, write to the Free Software Foundation, Inc., 51 Franklin
-Street, Fifth Floor, Boston, MA 02110-1301, USA.
-
-
-
-
This document was translated from LATEX by
-HEVEA.
-
diff --git a/doc/version.tex b/doc/version.tex
deleted file mode 100644
index 42cf7d828..000000000
--- a/doc/version.tex
+++ /dev/null
@@ -1,2 +0,0 @@
-% ejabberd version (automatically generated).
-\newcommand{\version}{3.0.0-alpha-x}
diff --git a/src/configure b/src/configure
deleted file mode 100755
index a71534543..000000000
--- a/src/configure
+++ /dev/null
@@ -1,5977 +0,0 @@
-#! /bin/sh
-# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.65 for ejabberd 3.0.0-alpha-x.
-#
-# Report bugs to .
-#
-#
-# Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
-# 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation,
-# Inc.
-#
-#
-# This configure script is free software; the Free Software Foundation
-# gives unlimited permission to copy, distribute and modify it.
-## -------------------- ##
-## M4sh Initialization. ##
-## -------------------- ##
-
-# Be more Bourne compatible
-DUALCASE=1; export DUALCASE # for MKS sh
-if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then :
- emulate sh
- NULLCMD=:
- # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
- # is contrary to our usage. Disable this feature.
- alias -g '${1+"$@"}'='"$@"'
- setopt NO_GLOB_SUBST
-else
- case `(set -o) 2>/dev/null` in #(
- *posix*) :
- set -o posix ;; #(
- *) :
- ;;
-esac
-fi
-
-
-as_nl='
-'
-export as_nl
-# Printing a long string crashes Solaris 7 /usr/bin/printf.
-as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
-as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
-as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
-# Prefer a ksh shell builtin over an external printf program on Solaris,
-# but without wasting forks for bash or zsh.
-if test -z "$BASH_VERSION$ZSH_VERSION" \
- && (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
- as_echo='print -r --'
- as_echo_n='print -rn --'
-elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
- as_echo='printf %s\n'
- as_echo_n='printf %s'
-else
- if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
- as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
- as_echo_n='/usr/ucb/echo -n'
- else
- as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
- as_echo_n_body='eval
- arg=$1;
- case $arg in #(
- *"$as_nl"*)
- expr "X$arg" : "X\\(.*\\)$as_nl";
- arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
- esac;
- expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
- '
- export as_echo_n_body
- as_echo_n='sh -c $as_echo_n_body as_echo'
- fi
- export as_echo_body
- as_echo='sh -c $as_echo_body as_echo'
-fi
-
-# The user is always right.
-if test "${PATH_SEPARATOR+set}" != set; then
- PATH_SEPARATOR=:
- (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
- (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
- PATH_SEPARATOR=';'
- }
-fi
-
-
-# IFS
-# We need space, tab and new line, in precisely that order. Quoting is
-# there to prevent editors from complaining about space-tab.
-# (If _AS_PATH_WALK were called with IFS unset, it would disable word
-# splitting by setting IFS to empty value.)
-IFS=" "" $as_nl"
-
-# Find who we are. Look in the path if we contain no directory separator.
-case $0 in #((
- *[\\/]* ) as_myself=$0 ;;
- *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
- done
-IFS=$as_save_IFS
-
- ;;
-esac
-# We did not find ourselves, most probably we were run as `sh COMMAND'
-# in which case we are not to be found in the path.
-if test "x$as_myself" = x; then
- as_myself=$0
-fi
-if test ! -f "$as_myself"; then
- $as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
- exit 1
-fi
-
-# Unset variables that we do not need and which cause bugs (e.g. in
-# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1"
-# suppresses any "Segmentation fault" message there. '((' could
-# trigger a bug in pdksh 5.2.14.
-for as_var in BASH_ENV ENV MAIL MAILPATH
-do eval test x\${$as_var+set} = xset \
- && ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || :
-done
-PS1='$ '
-PS2='> '
-PS4='+ '
-
-# NLS nuisances.
-LC_ALL=C
-export LC_ALL
-LANGUAGE=C
-export LANGUAGE
-
-# CDPATH.
-(unset CDPATH) >/dev/null 2>&1 && unset CDPATH
-
-if test "x$CONFIG_SHELL" = x; then
- as_bourne_compatible="if test -n \"\${ZSH_VERSION+set}\" && (emulate sh) >/dev/null 2>&1; then :
- emulate sh
- NULLCMD=:
- # Pre-4.2 versions of Zsh do word splitting on \${1+\"\$@\"}, which
- # is contrary to our usage. Disable this feature.
- alias -g '\${1+\"\$@\"}'='\"\$@\"'
- setopt NO_GLOB_SUBST
-else
- case \`(set -o) 2>/dev/null\` in #(
- *posix*) :
- set -o posix ;; #(
- *) :
- ;;
-esac
-fi
-"
- as_required="as_fn_return () { (exit \$1); }
-as_fn_success () { as_fn_return 0; }
-as_fn_failure () { as_fn_return 1; }
-as_fn_ret_success () { return 0; }
-as_fn_ret_failure () { return 1; }
-
-exitcode=0
-as_fn_success || { exitcode=1; echo as_fn_success failed.; }
-as_fn_failure && { exitcode=1; echo as_fn_failure succeeded.; }
-as_fn_ret_success || { exitcode=1; echo as_fn_ret_success failed.; }
-as_fn_ret_failure && { exitcode=1; echo as_fn_ret_failure succeeded.; }
-if ( set x; as_fn_ret_success y && test x = \"\$1\" ); then :
-
-else
- exitcode=1; echo positional parameters were not saved.
-fi
-test x\$exitcode = x0 || exit 1"
- as_suggested=" as_lineno_1=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_1a=\$LINENO
- as_lineno_2=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_2a=\$LINENO
- eval 'test \"x\$as_lineno_1'\$as_run'\" != \"x\$as_lineno_2'\$as_run'\" &&
- test \"x\`expr \$as_lineno_1'\$as_run' + 1\`\" = \"x\$as_lineno_2'\$as_run'\"' || exit 1
-test \$(( 1 + 1 )) = 2 || exit 1"
- if (eval "$as_required") 2>/dev/null; then :
- as_have_required=yes
-else
- as_have_required=no
-fi
- if test x$as_have_required = xyes && (eval "$as_suggested") 2>/dev/null; then :
-
-else
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-as_found=false
-for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- as_found=:
- case $as_dir in #(
- /*)
- for as_base in sh bash ksh sh5; do
- # Try only shells that exist, to save several forks.
- as_shell=$as_dir/$as_base
- if { test -f "$as_shell" || test -f "$as_shell.exe"; } &&
- { $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$as_shell"; } 2>/dev/null; then :
- CONFIG_SHELL=$as_shell as_have_required=yes
- if { $as_echo "$as_bourne_compatible""$as_suggested" | as_run=a "$as_shell"; } 2>/dev/null; then :
- break 2
-fi
-fi
- done;;
- esac
- as_found=false
-done
-$as_found || { if { test -f "$SHELL" || test -f "$SHELL.exe"; } &&
- { $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$SHELL"; } 2>/dev/null; then :
- CONFIG_SHELL=$SHELL as_have_required=yes
-fi; }
-IFS=$as_save_IFS
-
-
- if test "x$CONFIG_SHELL" != x; then :
- # We cannot yet assume a decent shell, so we have to provide a
- # neutralization value for shells without unset; and this also
- # works around shells that cannot unset nonexistent variables.
- BASH_ENV=/dev/null
- ENV=/dev/null
- (unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV
- export CONFIG_SHELL
- exec "$CONFIG_SHELL" "$as_myself" ${1+"$@"}
-fi
-
- if test x$as_have_required = xno; then :
- $as_echo "$0: This script requires a shell more modern than all"
- $as_echo "$0: the shells that I found on your system."
- if test x${ZSH_VERSION+set} = xset ; then
- $as_echo "$0: In particular, zsh $ZSH_VERSION has bugs and should"
- $as_echo "$0: be upgraded to zsh 4.3.4 or later."
- else
- $as_echo "$0: Please tell bug-autoconf@gnu.org and
-$0: ejabberd@process-one.net about your system, including
-$0: any error possibly output before this message. Then
-$0: install a modern shell, or manually run the script
-$0: under such a shell if you do have one."
- fi
- exit 1
-fi
-fi
-fi
-SHELL=${CONFIG_SHELL-/bin/sh}
-export SHELL
-# Unset more variables known to interfere with behavior of common tools.
-CLICOLOR_FORCE= GREP_OPTIONS=
-unset CLICOLOR_FORCE GREP_OPTIONS
-
-## --------------------- ##
-## M4sh Shell Functions. ##
-## --------------------- ##
-# as_fn_unset VAR
-# ---------------
-# Portably unset VAR.
-as_fn_unset ()
-{
- { eval $1=; unset $1;}
-}
-as_unset=as_fn_unset
-
-# as_fn_set_status STATUS
-# -----------------------
-# Set $? to STATUS, without forking.
-as_fn_set_status ()
-{
- return $1
-} # as_fn_set_status
-
-# as_fn_exit STATUS
-# -----------------
-# Exit the shell with STATUS, even in a "trap 0" or "set -e" context.
-as_fn_exit ()
-{
- set +e
- as_fn_set_status $1
- exit $1
-} # as_fn_exit
-
-# as_fn_mkdir_p
-# -------------
-# Create "$as_dir" as a directory, including parents if necessary.
-as_fn_mkdir_p ()
-{
-
- case $as_dir in #(
- -*) as_dir=./$as_dir;;
- esac
- test -d "$as_dir" || eval $as_mkdir_p || {
- as_dirs=
- while :; do
- case $as_dir in #(
- *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
- *) as_qdir=$as_dir;;
- esac
- as_dirs="'$as_qdir' $as_dirs"
- as_dir=`$as_dirname -- "$as_dir" ||
-$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$as_dir" : 'X\(//\)[^/]' \| \
- X"$as_dir" : 'X\(//\)$' \| \
- X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$as_dir" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- test -d "$as_dir" && break
- done
- test -z "$as_dirs" || eval "mkdir $as_dirs"
- } || test -d "$as_dir" || as_fn_error "cannot create directory $as_dir"
-
-
-} # as_fn_mkdir_p
-# as_fn_append VAR VALUE
-# ----------------------
-# Append the text in VALUE to the end of the definition contained in VAR. Take
-# advantage of any shell optimizations that allow amortized linear growth over
-# repeated appends, instead of the typical quadratic growth present in naive
-# implementations.
-if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then :
- eval 'as_fn_append ()
- {
- eval $1+=\$2
- }'
-else
- as_fn_append ()
- {
- eval $1=\$$1\$2
- }
-fi # as_fn_append
-
-# as_fn_arith ARG...
-# ------------------
-# Perform arithmetic evaluation on the ARGs, and store the result in the
-# global $as_val. Take advantage of shells that can avoid forks. The arguments
-# must be portable across $(()) and expr.
-if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then :
- eval 'as_fn_arith ()
- {
- as_val=$(( $* ))
- }'
-else
- as_fn_arith ()
- {
- as_val=`expr "$@" || test $? -eq 1`
- }
-fi # as_fn_arith
-
-
-# as_fn_error ERROR [LINENO LOG_FD]
-# ---------------------------------
-# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are
-# provided, also output the error to LOG_FD, referencing LINENO. Then exit the
-# script with status $?, using 1 if that was 0.
-as_fn_error ()
-{
- as_status=$?; test $as_status -eq 0 && as_status=1
- if test "$3"; then
- as_lineno=${as_lineno-"$2"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
- $as_echo "$as_me:${as_lineno-$LINENO}: error: $1" >&$3
- fi
- $as_echo "$as_me: error: $1" >&2
- as_fn_exit $as_status
-} # as_fn_error
-
-if expr a : '\(a\)' >/dev/null 2>&1 &&
- test "X`expr 00001 : '.*\(...\)'`" = X001; then
- as_expr=expr
-else
- as_expr=false
-fi
-
-if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
- as_basename=basename
-else
- as_basename=false
-fi
-
-if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
- as_dirname=dirname
-else
- as_dirname=false
-fi
-
-as_me=`$as_basename -- "$0" ||
-$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
- X"$0" : 'X\(//\)$' \| \
- X"$0" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X/"$0" |
- sed '/^.*\/\([^/][^/]*\)\/*$/{
- s//\1/
- q
- }
- /^X\/\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\/\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
-
-# Avoid depending upon Character Ranges.
-as_cr_letters='abcdefghijklmnopqrstuvwxyz'
-as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
-as_cr_Letters=$as_cr_letters$as_cr_LETTERS
-as_cr_digits='0123456789'
-as_cr_alnum=$as_cr_Letters$as_cr_digits
-
-
- as_lineno_1=$LINENO as_lineno_1a=$LINENO
- as_lineno_2=$LINENO as_lineno_2a=$LINENO
- eval 'test "x$as_lineno_1'$as_run'" != "x$as_lineno_2'$as_run'" &&
- test "x`expr $as_lineno_1'$as_run' + 1`" = "x$as_lineno_2'$as_run'"' || {
- # Blame Lee E. McMahon (1931-1989) for sed's syntax. :-)
- sed -n '
- p
- /[$]LINENO/=
- ' <$as_myself |
- sed '
- s/[$]LINENO.*/&-/
- t lineno
- b
- :lineno
- N
- :loop
- s/[$]LINENO\([^'$as_cr_alnum'_].*\n\)\(.*\)/\2\1\2/
- t loop
- s/-\n.*//
- ' >$as_me.lineno &&
- chmod +x "$as_me.lineno" ||
- { $as_echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2; as_fn_exit 1; }
-
- # Don't try to exec as it changes $[0], causing all sort of problems
- # (the dirname of $[0] is not the place where we might find the
- # original and so on. Autoconf is especially sensitive to this).
- . "./$as_me.lineno"
- # Exit status is that of the last command.
- exit
-}
-
-ECHO_C= ECHO_N= ECHO_T=
-case `echo -n x` in #(((((
--n*)
- case `echo 'xy\c'` in
- *c*) ECHO_T=' ';; # ECHO_T is single tab character.
- xy) ECHO_C='\c';;
- *) echo `echo ksh88 bug on AIX 6.1` > /dev/null
- ECHO_T=' ';;
- esac;;
-*)
- ECHO_N='-n';;
-esac
-
-rm -f conf$$ conf$$.exe conf$$.file
-if test -d conf$$.dir; then
- rm -f conf$$.dir/conf$$.file
-else
- rm -f conf$$.dir
- mkdir conf$$.dir 2>/dev/null
-fi
-if (echo >conf$$.file) 2>/dev/null; then
- if ln -s conf$$.file conf$$ 2>/dev/null; then
- as_ln_s='ln -s'
- # ... but there are two gotchas:
- # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
- # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
- # In both cases, we have to default to `cp -p'.
- ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
- as_ln_s='cp -p'
- elif ln conf$$.file conf$$ 2>/dev/null; then
- as_ln_s=ln
- else
- as_ln_s='cp -p'
- fi
-else
- as_ln_s='cp -p'
-fi
-rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
-rmdir conf$$.dir 2>/dev/null
-
-if mkdir -p . 2>/dev/null; then
- as_mkdir_p='mkdir -p "$as_dir"'
-else
- test -d ./-p && rmdir ./-p
- as_mkdir_p=false
-fi
-
-if test -x / >/dev/null 2>&1; then
- as_test_x='test -x'
-else
- if ls -dL / >/dev/null 2>&1; then
- as_ls_L_option=L
- else
- as_ls_L_option=
- fi
- as_test_x='
- eval sh -c '\''
- if test -d "$1"; then
- test -d "$1/.";
- else
- case $1 in #(
- -*)set "./$1";;
- esac;
- case `ls -ld'$as_ls_L_option' "$1" 2>/dev/null` in #((
- ???[sx]*):;;*)false;;esac;fi
- '\'' sh
- '
-fi
-as_executable_p=$as_test_x
-
-# Sed expression to map a string onto a valid CPP name.
-as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
-
-# Sed expression to map a string onto a valid variable name.
-as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
-
-
-test -n "$DJDIR" || exec 7<&0 &1
-
-# Name of the host.
-# hostname on some systems (SVR3.2, Linux) returns a bogus exit status,
-# so uname gets run too.
-ac_hostname=`(hostname || uname -n) 2>/dev/null | sed 1q`
-
-#
-# Initializations.
-#
-ac_default_prefix=/usr/local
-ac_clean_files=
-ac_config_libobj_dir=.
-LIBOBJS=
-cross_compiling=no
-subdirs=
-MFLAGS=
-MAKEFLAGS=
-
-# Identity of this package.
-PACKAGE_NAME='ejabberd'
-PACKAGE_TARNAME='ejabberd'
-PACKAGE_VERSION='3.0.0-alpha-x'
-PACKAGE_STRING='ejabberd 3.0.0-alpha-x'
-PACKAGE_BUGREPORT='ejabberd@process-one.net'
-PACKAGE_URL=''
-
-ac_default_prefix=/
-# Factoring default headers for most tests.
-ac_includes_default="\
-#include
-#ifdef HAVE_SYS_TYPES_H
-# include
-#endif
-#ifdef HAVE_SYS_STAT_H
-# include
-#endif
-#ifdef STDC_HEADERS
-# include
-# include
-#else
-# ifdef HAVE_STDLIB_H
-# include
-# endif
-#endif
-#ifdef HAVE_STRING_H
-# if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-# include
-# endif
-# include
-#endif
-#ifdef HAVE_STRINGS_H
-# include
-#endif
-#ifdef HAVE_INTTYPES_H
-# include
-#endif
-#ifdef HAVE_STDINT_H
-# include
-#endif
-#ifdef HAVE_UNISTD_H
-# include
-#endif"
-
-ac_subst_vars='LTLIBOBJS
-ERLCFLAGS
-target_os
-target_vendor
-target_cpu
-target
-host_os
-host_vendor
-host_cpu
-host
-build_os
-build_vendor
-build_cpu
-build
-md2
-INSTALLUSER
-SSL_CFLAGS
-SSL_LIBS
-full_xml
-transient_supervisors
-db_type
-roster_gateway_workaround
-hipe
-PAM_LIBS
-PAM_CFLAGS
-make_pam
-pam
-ZLIB_LIBS
-ZLIB_CFLAGS
-make_ejabberd_zlib
-ejabberd_zlib
-make_web
-web
-make_tls
-tls
-make_odbc
-odbc
-make_eldap
-eldap
-make_mod_pubsub
-mod_pubsub
-make_mod_proxy65
-mod_proxy65
-make_mod_muc
-mod_muc
-LIBOBJS
-EGREP
-GREP
-CPP
-ERLANG_EXMPP
-ERLANG_LIBS
-ERLANG_CFLAGS
-ERL
-ERLC
-SET_MAKE
-OBJEXT
-EXEEXT
-ac_ct_CC
-CPPFLAGS
-LDFLAGS
-CFLAGS
-CC
-target_alias
-host_alias
-build_alias
-LIBS
-ECHO_T
-ECHO_N
-ECHO_C
-DEFS
-mandir
-localedir
-libdir
-psdir
-pdfdir
-dvidir
-htmldir
-infodir
-docdir
-oldincludedir
-includedir
-localstatedir
-sharedstatedir
-sysconfdir
-datadir
-datarootdir
-libexecdir
-sbindir
-bindir
-program_transform_name
-prefix
-exec_prefix
-PACKAGE_URL
-PACKAGE_BUGREPORT
-PACKAGE_STRING
-PACKAGE_VERSION
-PACKAGE_TARNAME
-PACKAGE_NAME
-PATH_SEPARATOR
-SHELL'
-ac_subst_files=''
-ac_user_opts='
-enable_option_checking
-with_erlang
-enable_mod_muc
-enable_mod_proxy65
-enable_mod_pubsub
-enable_eldap
-enable_odbc
-enable_tls
-enable_web
-enable_ejabberd_zlib
-with_zlib
-enable_pam
-with_pam
-enable_hipe
-enable_roster_gateway_workaround
-enable_mssql
-enable_transient_supervisors
-enable_full_xml
-with_openssl
-enable_user
-'
- ac_precious_vars='build_alias
-host_alias
-target_alias
-CC
-CFLAGS
-LDFLAGS
-LIBS
-CPPFLAGS
-CPP
-ERLC
-ERLCFLAGS'
-
-
-# Initialize some variables set by options.
-ac_init_help=
-ac_init_version=false
-ac_unrecognized_opts=
-ac_unrecognized_sep=
-# The variables have the same names as the options, with
-# dashes changed to underlines.
-cache_file=/dev/null
-exec_prefix=NONE
-no_create=
-no_recursion=
-prefix=NONE
-program_prefix=NONE
-program_suffix=NONE
-program_transform_name=s,x,x,
-silent=
-site=
-srcdir=
-verbose=
-x_includes=NONE
-x_libraries=NONE
-
-# Installation directory options.
-# These are left unexpanded so users can "make install exec_prefix=/foo"
-# and all the variables that are supposed to be based on exec_prefix
-# by default will actually change.
-# Use braces instead of parens because sh, perl, etc. also accept them.
-# (The list follows the same order as the GNU Coding Standards.)
-bindir='${exec_prefix}/bin'
-sbindir='${exec_prefix}/sbin'
-libexecdir='${exec_prefix}/libexec'
-datarootdir='${prefix}/share'
-datadir='${datarootdir}'
-sysconfdir='${prefix}/etc'
-sharedstatedir='${prefix}/com'
-localstatedir='${prefix}/var'
-includedir='${prefix}/include'
-oldincludedir='/usr/include'
-docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
-infodir='${datarootdir}/info'
-htmldir='${docdir}'
-dvidir='${docdir}'
-pdfdir='${docdir}'
-psdir='${docdir}'
-libdir='${exec_prefix}/lib'
-localedir='${datarootdir}/locale'
-mandir='${datarootdir}/man'
-
-ac_prev=
-ac_dashdash=
-for ac_option
-do
- # If the previous option needs an argument, assign it.
- if test -n "$ac_prev"; then
- eval $ac_prev=\$ac_option
- ac_prev=
- continue
- fi
-
- case $ac_option in
- *=*) ac_optarg=`expr "X$ac_option" : '[^=]*=\(.*\)'` ;;
- *) ac_optarg=yes ;;
- esac
-
- # Accept the important Cygnus configure options, so we can diagnose typos.
-
- case $ac_dashdash$ac_option in
- --)
- ac_dashdash=yes ;;
-
- -bindir | --bindir | --bindi | --bind | --bin | --bi)
- ac_prev=bindir ;;
- -bindir=* | --bindir=* | --bindi=* | --bind=* | --bin=* | --bi=*)
- bindir=$ac_optarg ;;
-
- -build | --build | --buil | --bui | --bu)
- ac_prev=build_alias ;;
- -build=* | --build=* | --buil=* | --bui=* | --bu=*)
- build_alias=$ac_optarg ;;
-
- -cache-file | --cache-file | --cache-fil | --cache-fi \
- | --cache-f | --cache- | --cache | --cach | --cac | --ca | --c)
- ac_prev=cache_file ;;
- -cache-file=* | --cache-file=* | --cache-fil=* | --cache-fi=* \
- | --cache-f=* | --cache-=* | --cache=* | --cach=* | --cac=* | --ca=* | --c=*)
- cache_file=$ac_optarg ;;
-
- --config-cache | -C)
- cache_file=config.cache ;;
-
- -datadir | --datadir | --datadi | --datad)
- ac_prev=datadir ;;
- -datadir=* | --datadir=* | --datadi=* | --datad=*)
- datadir=$ac_optarg ;;
-
- -datarootdir | --datarootdir | --datarootdi | --datarootd | --dataroot \
- | --dataroo | --dataro | --datar)
- ac_prev=datarootdir ;;
- -datarootdir=* | --datarootdir=* | --datarootdi=* | --datarootd=* \
- | --dataroot=* | --dataroo=* | --dataro=* | --datar=*)
- datarootdir=$ac_optarg ;;
-
- -disable-* | --disable-*)
- ac_useropt=`expr "x$ac_option" : 'x-*disable-\(.*\)'`
- # Reject names that are not valid shell variable names.
- expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
- as_fn_error "invalid feature name: $ac_useropt"
- ac_useropt_orig=$ac_useropt
- ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
- case $ac_user_opts in
- *"
-"enable_$ac_useropt"
-"*) ;;
- *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--disable-$ac_useropt_orig"
- ac_unrecognized_sep=', ';;
- esac
- eval enable_$ac_useropt=no ;;
-
- -docdir | --docdir | --docdi | --doc | --do)
- ac_prev=docdir ;;
- -docdir=* | --docdir=* | --docdi=* | --doc=* | --do=*)
- docdir=$ac_optarg ;;
-
- -dvidir | --dvidir | --dvidi | --dvid | --dvi | --dv)
- ac_prev=dvidir ;;
- -dvidir=* | --dvidir=* | --dvidi=* | --dvid=* | --dvi=* | --dv=*)
- dvidir=$ac_optarg ;;
-
- -enable-* | --enable-*)
- ac_useropt=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'`
- # Reject names that are not valid shell variable names.
- expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
- as_fn_error "invalid feature name: $ac_useropt"
- ac_useropt_orig=$ac_useropt
- ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
- case $ac_user_opts in
- *"
-"enable_$ac_useropt"
-"*) ;;
- *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--enable-$ac_useropt_orig"
- ac_unrecognized_sep=', ';;
- esac
- eval enable_$ac_useropt=\$ac_optarg ;;
-
- -exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \
- | --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \
- | --exec | --exe | --ex)
- ac_prev=exec_prefix ;;
- -exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* \
- | --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* \
- | --exec=* | --exe=* | --ex=*)
- exec_prefix=$ac_optarg ;;
-
- -gas | --gas | --ga | --g)
- # Obsolete; use --with-gas.
- with_gas=yes ;;
-
- -help | --help | --hel | --he | -h)
- ac_init_help=long ;;
- -help=r* | --help=r* | --hel=r* | --he=r* | -hr*)
- ac_init_help=recursive ;;
- -help=s* | --help=s* | --hel=s* | --he=s* | -hs*)
- ac_init_help=short ;;
-
- -host | --host | --hos | --ho)
- ac_prev=host_alias ;;
- -host=* | --host=* | --hos=* | --ho=*)
- host_alias=$ac_optarg ;;
-
- -htmldir | --htmldir | --htmldi | --htmld | --html | --htm | --ht)
- ac_prev=htmldir ;;
- -htmldir=* | --htmldir=* | --htmldi=* | --htmld=* | --html=* | --htm=* \
- | --ht=*)
- htmldir=$ac_optarg ;;
-
- -includedir | --includedir | --includedi | --included | --include \
- | --includ | --inclu | --incl | --inc)
- ac_prev=includedir ;;
- -includedir=* | --includedir=* | --includedi=* | --included=* | --include=* \
- | --includ=* | --inclu=* | --incl=* | --inc=*)
- includedir=$ac_optarg ;;
-
- -infodir | --infodir | --infodi | --infod | --info | --inf)
- ac_prev=infodir ;;
- -infodir=* | --infodir=* | --infodi=* | --infod=* | --info=* | --inf=*)
- infodir=$ac_optarg ;;
-
- -libdir | --libdir | --libdi | --libd)
- ac_prev=libdir ;;
- -libdir=* | --libdir=* | --libdi=* | --libd=*)
- libdir=$ac_optarg ;;
-
- -libexecdir | --libexecdir | --libexecdi | --libexecd | --libexec \
- | --libexe | --libex | --libe)
- ac_prev=libexecdir ;;
- -libexecdir=* | --libexecdir=* | --libexecdi=* | --libexecd=* | --libexec=* \
- | --libexe=* | --libex=* | --libe=*)
- libexecdir=$ac_optarg ;;
-
- -localedir | --localedir | --localedi | --localed | --locale)
- ac_prev=localedir ;;
- -localedir=* | --localedir=* | --localedi=* | --localed=* | --locale=*)
- localedir=$ac_optarg ;;
-
- -localstatedir | --localstatedir | --localstatedi | --localstated \
- | --localstate | --localstat | --localsta | --localst | --locals)
- ac_prev=localstatedir ;;
- -localstatedir=* | --localstatedir=* | --localstatedi=* | --localstated=* \
- | --localstate=* | --localstat=* | --localsta=* | --localst=* | --locals=*)
- localstatedir=$ac_optarg ;;
-
- -mandir | --mandir | --mandi | --mand | --man | --ma | --m)
- ac_prev=mandir ;;
- -mandir=* | --mandir=* | --mandi=* | --mand=* | --man=* | --ma=* | --m=*)
- mandir=$ac_optarg ;;
-
- -nfp | --nfp | --nf)
- # Obsolete; use --without-fp.
- with_fp=no ;;
-
- -no-create | --no-create | --no-creat | --no-crea | --no-cre \
- | --no-cr | --no-c | -n)
- no_create=yes ;;
-
- -no-recursion | --no-recursion | --no-recursio | --no-recursi \
- | --no-recurs | --no-recur | --no-recu | --no-rec | --no-re | --no-r)
- no_recursion=yes ;;
-
- -oldincludedir | --oldincludedir | --oldincludedi | --oldincluded \
- | --oldinclude | --oldinclud | --oldinclu | --oldincl | --oldinc \
- | --oldin | --oldi | --old | --ol | --o)
- ac_prev=oldincludedir ;;
- -oldincludedir=* | --oldincludedir=* | --oldincludedi=* | --oldincluded=* \
- | --oldinclude=* | --oldinclud=* | --oldinclu=* | --oldincl=* | --oldinc=* \
- | --oldin=* | --oldi=* | --old=* | --ol=* | --o=*)
- oldincludedir=$ac_optarg ;;
-
- -prefix | --prefix | --prefi | --pref | --pre | --pr | --p)
- ac_prev=prefix ;;
- -prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*)
- prefix=$ac_optarg ;;
-
- -program-prefix | --program-prefix | --program-prefi | --program-pref \
- | --program-pre | --program-pr | --program-p)
- ac_prev=program_prefix ;;
- -program-prefix=* | --program-prefix=* | --program-prefi=* \
- | --program-pref=* | --program-pre=* | --program-pr=* | --program-p=*)
- program_prefix=$ac_optarg ;;
-
- -program-suffix | --program-suffix | --program-suffi | --program-suff \
- | --program-suf | --program-su | --program-s)
- ac_prev=program_suffix ;;
- -program-suffix=* | --program-suffix=* | --program-suffi=* \
- | --program-suff=* | --program-suf=* | --program-su=* | --program-s=*)
- program_suffix=$ac_optarg ;;
-
- -program-transform-name | --program-transform-name \
- | --program-transform-nam | --program-transform-na \
- | --program-transform-n | --program-transform- \
- | --program-transform | --program-transfor \
- | --program-transfo | --program-transf \
- | --program-trans | --program-tran \
- | --progr-tra | --program-tr | --program-t)
- ac_prev=program_transform_name ;;
- -program-transform-name=* | --program-transform-name=* \
- | --program-transform-nam=* | --program-transform-na=* \
- | --program-transform-n=* | --program-transform-=* \
- | --program-transform=* | --program-transfor=* \
- | --program-transfo=* | --program-transf=* \
- | --program-trans=* | --program-tran=* \
- | --progr-tra=* | --program-tr=* | --program-t=*)
- program_transform_name=$ac_optarg ;;
-
- -pdfdir | --pdfdir | --pdfdi | --pdfd | --pdf | --pd)
- ac_prev=pdfdir ;;
- -pdfdir=* | --pdfdir=* | --pdfdi=* | --pdfd=* | --pdf=* | --pd=*)
- pdfdir=$ac_optarg ;;
-
- -psdir | --psdir | --psdi | --psd | --ps)
- ac_prev=psdir ;;
- -psdir=* | --psdir=* | --psdi=* | --psd=* | --ps=*)
- psdir=$ac_optarg ;;
-
- -q | -quiet | --quiet | --quie | --qui | --qu | --q \
- | -silent | --silent | --silen | --sile | --sil)
- silent=yes ;;
-
- -sbindir | --sbindir | --sbindi | --sbind | --sbin | --sbi | --sb)
- ac_prev=sbindir ;;
- -sbindir=* | --sbindir=* | --sbindi=* | --sbind=* | --sbin=* \
- | --sbi=* | --sb=*)
- sbindir=$ac_optarg ;;
-
- -sharedstatedir | --sharedstatedir | --sharedstatedi \
- | --sharedstated | --sharedstate | --sharedstat | --sharedsta \
- | --sharedst | --shareds | --shared | --share | --shar \
- | --sha | --sh)
- ac_prev=sharedstatedir ;;
- -sharedstatedir=* | --sharedstatedir=* | --sharedstatedi=* \
- | --sharedstated=* | --sharedstate=* | --sharedstat=* | --sharedsta=* \
- | --sharedst=* | --shareds=* | --shared=* | --share=* | --shar=* \
- | --sha=* | --sh=*)
- sharedstatedir=$ac_optarg ;;
-
- -site | --site | --sit)
- ac_prev=site ;;
- -site=* | --site=* | --sit=*)
- site=$ac_optarg ;;
-
- -srcdir | --srcdir | --srcdi | --srcd | --src | --sr)
- ac_prev=srcdir ;;
- -srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*)
- srcdir=$ac_optarg ;;
-
- -sysconfdir | --sysconfdir | --sysconfdi | --sysconfd | --sysconf \
- | --syscon | --sysco | --sysc | --sys | --sy)
- ac_prev=sysconfdir ;;
- -sysconfdir=* | --sysconfdir=* | --sysconfdi=* | --sysconfd=* | --sysconf=* \
- | --syscon=* | --sysco=* | --sysc=* | --sys=* | --sy=*)
- sysconfdir=$ac_optarg ;;
-
- -target | --target | --targe | --targ | --tar | --ta | --t)
- ac_prev=target_alias ;;
- -target=* | --target=* | --targe=* | --targ=* | --tar=* | --ta=* | --t=*)
- target_alias=$ac_optarg ;;
-
- -v | -verbose | --verbose | --verbos | --verbo | --verb)
- verbose=yes ;;
-
- -version | --version | --versio | --versi | --vers | -V)
- ac_init_version=: ;;
-
- -with-* | --with-*)
- ac_useropt=`expr "x$ac_option" : 'x-*with-\([^=]*\)'`
- # Reject names that are not valid shell variable names.
- expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
- as_fn_error "invalid package name: $ac_useropt"
- ac_useropt_orig=$ac_useropt
- ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
- case $ac_user_opts in
- *"
-"with_$ac_useropt"
-"*) ;;
- *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--with-$ac_useropt_orig"
- ac_unrecognized_sep=', ';;
- esac
- eval with_$ac_useropt=\$ac_optarg ;;
-
- -without-* | --without-*)
- ac_useropt=`expr "x$ac_option" : 'x-*without-\(.*\)'`
- # Reject names that are not valid shell variable names.
- expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
- as_fn_error "invalid package name: $ac_useropt"
- ac_useropt_orig=$ac_useropt
- ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
- case $ac_user_opts in
- *"
-"with_$ac_useropt"
-"*) ;;
- *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--without-$ac_useropt_orig"
- ac_unrecognized_sep=', ';;
- esac
- eval with_$ac_useropt=no ;;
-
- --x)
- # Obsolete; use --with-x.
- with_x=yes ;;
-
- -x-includes | --x-includes | --x-include | --x-includ | --x-inclu \
- | --x-incl | --x-inc | --x-in | --x-i)
- ac_prev=x_includes ;;
- -x-includes=* | --x-includes=* | --x-include=* | --x-includ=* | --x-inclu=* \
- | --x-incl=* | --x-inc=* | --x-in=* | --x-i=*)
- x_includes=$ac_optarg ;;
-
- -x-libraries | --x-libraries | --x-librarie | --x-librari \
- | --x-librar | --x-libra | --x-libr | --x-lib | --x-li | --x-l)
- ac_prev=x_libraries ;;
- -x-libraries=* | --x-libraries=* | --x-librarie=* | --x-librari=* \
- | --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*)
- x_libraries=$ac_optarg ;;
-
- -*) as_fn_error "unrecognized option: \`$ac_option'
-Try \`$0 --help' for more information."
- ;;
-
- *=*)
- ac_envvar=`expr "x$ac_option" : 'x\([^=]*\)='`
- # Reject names that are not valid shell variable names.
- case $ac_envvar in #(
- '' | [0-9]* | *[!_$as_cr_alnum]* )
- as_fn_error "invalid variable name: \`$ac_envvar'" ;;
- esac
- eval $ac_envvar=\$ac_optarg
- export $ac_envvar ;;
-
- *)
- # FIXME: should be removed in autoconf 3.0.
- $as_echo "$as_me: WARNING: you should use --build, --host, --target" >&2
- expr "x$ac_option" : ".*[^-._$as_cr_alnum]" >/dev/null &&
- $as_echo "$as_me: WARNING: invalid host type: $ac_option" >&2
- : ${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option}
- ;;
-
- esac
-done
-
-if test -n "$ac_prev"; then
- ac_option=--`echo $ac_prev | sed 's/_/-/g'`
- as_fn_error "missing argument to $ac_option"
-fi
-
-if test -n "$ac_unrecognized_opts"; then
- case $enable_option_checking in
- no) ;;
- fatal) as_fn_error "unrecognized options: $ac_unrecognized_opts" ;;
- *) $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2 ;;
- esac
-fi
-
-# Check all directory arguments for consistency.
-for ac_var in exec_prefix prefix bindir sbindir libexecdir datarootdir \
- datadir sysconfdir sharedstatedir localstatedir includedir \
- oldincludedir docdir infodir htmldir dvidir pdfdir psdir \
- libdir localedir mandir
-do
- eval ac_val=\$$ac_var
- # Remove trailing slashes.
- case $ac_val in
- */ )
- ac_val=`expr "X$ac_val" : 'X\(.*[^/]\)' \| "X$ac_val" : 'X\(.*\)'`
- eval $ac_var=\$ac_val;;
- esac
- # Be sure to have absolute directory names.
- case $ac_val in
- [\\/$]* | ?:[\\/]* ) continue;;
- NONE | '' ) case $ac_var in *prefix ) continue;; esac;;
- esac
- as_fn_error "expected an absolute directory name for --$ac_var: $ac_val"
-done
-
-# There might be people who depend on the old broken behavior: `$host'
-# used to hold the argument of --host etc.
-# FIXME: To remove some day.
-build=$build_alias
-host=$host_alias
-target=$target_alias
-
-# FIXME: To remove some day.
-if test "x$host_alias" != x; then
- if test "x$build_alias" = x; then
- cross_compiling=maybe
- $as_echo "$as_me: WARNING: If you wanted to set the --build type, don't use --host.
- If a cross compiler is detected then cross compile mode will be used." >&2
- elif test "x$build_alias" != "x$host_alias"; then
- cross_compiling=yes
- fi
-fi
-
-ac_tool_prefix=
-test -n "$host_alias" && ac_tool_prefix=$host_alias-
-
-test "$silent" = yes && exec 6>/dev/null
-
-
-ac_pwd=`pwd` && test -n "$ac_pwd" &&
-ac_ls_di=`ls -di .` &&
-ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||
- as_fn_error "working directory cannot be determined"
-test "X$ac_ls_di" = "X$ac_pwd_ls_di" ||
- as_fn_error "pwd does not report name of working directory"
-
-
-# Find the source files, if location was not specified.
-if test -z "$srcdir"; then
- ac_srcdir_defaulted=yes
- # Try the directory containing this script, then the parent directory.
- ac_confdir=`$as_dirname -- "$as_myself" ||
-$as_expr X"$as_myself" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$as_myself" : 'X\(//\)[^/]' \| \
- X"$as_myself" : 'X\(//\)$' \| \
- X"$as_myself" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$as_myself" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- srcdir=$ac_confdir
- if test ! -r "$srcdir/$ac_unique_file"; then
- srcdir=..
- fi
-else
- ac_srcdir_defaulted=no
-fi
-if test ! -r "$srcdir/$ac_unique_file"; then
- test "$ac_srcdir_defaulted" = yes && srcdir="$ac_confdir or .."
- as_fn_error "cannot find sources ($ac_unique_file) in $srcdir"
-fi
-ac_msg="sources are in $srcdir, but \`cd $srcdir' does not work"
-ac_abs_confdir=`(
- cd "$srcdir" && test -r "./$ac_unique_file" || as_fn_error "$ac_msg"
- pwd)`
-# When building in place, set srcdir=.
-if test "$ac_abs_confdir" = "$ac_pwd"; then
- srcdir=.
-fi
-# Remove unnecessary trailing slashes from srcdir.
-# Double slashes in file names in object file debugging info
-# mess up M-x gdb in Emacs.
-case $srcdir in
-*/) srcdir=`expr "X$srcdir" : 'X\(.*[^/]\)' \| "X$srcdir" : 'X\(.*\)'`;;
-esac
-for ac_var in $ac_precious_vars; do
- eval ac_env_${ac_var}_set=\${${ac_var}+set}
- eval ac_env_${ac_var}_value=\$${ac_var}
- eval ac_cv_env_${ac_var}_set=\${${ac_var}+set}
- eval ac_cv_env_${ac_var}_value=\$${ac_var}
-done
-
-#
-# Report the --help message.
-#
-if test "$ac_init_help" = "long"; then
- # Omit some internal or obsolete options to make the list less imposing.
- # This message is too long to be a string in the A/UX 3.1 sh.
- cat <<_ACEOF
-\`configure' configures ejabberd 3.0.0-alpha-x to adapt to many kinds of systems.
-
-Usage: $0 [OPTION]... [VAR=VALUE]...
-
-To assign environment variables (e.g., CC, CFLAGS...), specify them as
-VAR=VALUE. See below for descriptions of some of the useful variables.
-
-Defaults for the options are specified in brackets.
-
-Configuration:
- -h, --help display this help and exit
- --help=short display options specific to this package
- --help=recursive display the short help of all the included packages
- -V, --version display version information and exit
- -q, --quiet, --silent do not print \`checking...' messages
- --cache-file=FILE cache test results in FILE [disabled]
- -C, --config-cache alias for \`--cache-file=config.cache'
- -n, --no-create do not create output files
- --srcdir=DIR find the sources in DIR [configure dir or \`..']
-
-Installation directories:
- --prefix=PREFIX install architecture-independent files in PREFIX
- [$ac_default_prefix]
- --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
- [PREFIX]
-
-By default, \`make install' will install all the files in
-\`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc. You can specify
-an installation prefix other than \`$ac_default_prefix' using \`--prefix',
-for instance \`--prefix=\$HOME'.
-
-For better control, use the options below.
-
-Fine tuning of the installation directories:
- --bindir=DIR user executables [EPREFIX/bin]
- --sbindir=DIR system admin executables [EPREFIX/sbin]
- --libexecdir=DIR program executables [EPREFIX/libexec]
- --sysconfdir=DIR read-only single-machine data [PREFIX/etc]
- --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
- --localstatedir=DIR modifiable single-machine data [PREFIX/var]
- --libdir=DIR object code libraries [EPREFIX/lib]
- --includedir=DIR C header files [PREFIX/include]
- --oldincludedir=DIR C header files for non-gcc [/usr/include]
- --datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
- --datadir=DIR read-only architecture-independent data [DATAROOTDIR]
- --infodir=DIR info documentation [DATAROOTDIR/info]
- --localedir=DIR locale-dependent data [DATAROOTDIR/locale]
- --mandir=DIR man documentation [DATAROOTDIR/man]
- --docdir=DIR documentation root [DATAROOTDIR/doc/ejabberd]
- --htmldir=DIR html documentation [DOCDIR]
- --dvidir=DIR dvi documentation [DOCDIR]
- --pdfdir=DIR pdf documentation [DOCDIR]
- --psdir=DIR ps documentation [DOCDIR]
-_ACEOF
-
- cat <<\_ACEOF
-
-System types:
- --build=BUILD configure for building on BUILD [guessed]
- --host=HOST cross-compile to build programs to run on HOST [BUILD]
- --target=TARGET configure for building compilers for TARGET [HOST]
-_ACEOF
-fi
-
-if test -n "$ac_init_help"; then
- case $ac_init_help in
- short | recursive ) echo "Configuration of ejabberd 3.0.0-alpha-x:";;
- esac
- cat <<\_ACEOF
-
-Optional Features:
- --disable-option-checking ignore unrecognized --enable/--with options
- --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
- --enable-FEATURE[=ARG] include FEATURE [ARG=yes]
- --enable-mod_muc enable mod_muc (default: yes)
- --enable-mod_proxy65 enable mod_proxy65 (default: yes)
- --enable-mod_pubsub enable mod_pubsub (default: yes)
- --enable-eldap enable eldap (default: yes)
- --enable-odbc enable odbc (default: no)
- --enable-tls enable tls (default: yes)
- --enable-web enable web (default: yes)
- --enable-ejabberd_zlib enable ejabberd_zlib (default: yes)
- --enable-pam enable pam (default: no)
- --enable-hipe compile natively with HiPE, not recommended
- (default: no)
- --enable-roster-gateway-workaround
- turn on workaround for processing gateway
- subscriptions (default: no)
- --enable-mssql use Microsoft SQL Server database (default: no,
- requires --enable-odbc)
- --enable-transient_supervisors
- use Erlang supervision for transient process
- (default: yes)
- --enable-full-xml use XML features in XMPP stream (ex: CDATA)
- (default: no, requires XML compliant clients)
- --enable-user[[[=USER]]]
- allow this system user to start ejabberd (default:
- no)
-
-Optional Packages:
- --with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
- --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
- --with-erlang=PREFIX path to erlc and erl
- --with-zlib=PREFIX prefix where zlib is installed
- --with-pam=PREFIX prefix where PAM is installed
- --with-openssl=PREFIX prefix where OPENSSL is installed
-
-Some influential environment variables:
- CC C compiler command
- CFLAGS C compiler flags
- LDFLAGS linker flags, e.g. -L if you have libraries in a
- nonstandard directory
- LIBS libraries to pass to the linker, e.g. -l
- CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I if
- you have headers in a nonstandard directory
- CPP C preprocessor
- ERLC Erlang/OTP compiler command [autodetected]
- ERLCFLAGS Erlang/OTP compiler flags [none]
-
-Use these variables to override the choices made by `configure' or to help
-it to find libraries and programs with nonstandard names/locations.
-
-Report bugs to .
-_ACEOF
-ac_status=$?
-fi
-
-if test "$ac_init_help" = "recursive"; then
- # If there are subdirs, report their specific --help.
- for ac_dir in : $ac_subdirs_all; do test "x$ac_dir" = x: && continue
- test -d "$ac_dir" ||
- { cd "$srcdir" && ac_pwd=`pwd` && srcdir=. && test -d "$ac_dir"; } ||
- continue
- ac_builddir=.
-
-case "$ac_dir" in
-.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
-*)
- ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
- # A ".." for each directory in $ac_dir_suffix.
- ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
- case $ac_top_builddir_sub in
- "") ac_top_builddir_sub=. ac_top_build_prefix= ;;
- *) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
- esac ;;
-esac
-ac_abs_top_builddir=$ac_pwd
-ac_abs_builddir=$ac_pwd$ac_dir_suffix
-# for backward compatibility:
-ac_top_builddir=$ac_top_build_prefix
-
-case $srcdir in
- .) # We are building in place.
- ac_srcdir=.
- ac_top_srcdir=$ac_top_builddir_sub
- ac_abs_top_srcdir=$ac_pwd ;;
- [\\/]* | ?:[\\/]* ) # Absolute name.
- ac_srcdir=$srcdir$ac_dir_suffix;
- ac_top_srcdir=$srcdir
- ac_abs_top_srcdir=$srcdir ;;
- *) # Relative name.
- ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
- ac_top_srcdir=$ac_top_build_prefix$srcdir
- ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
-esac
-ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
-
- cd "$ac_dir" || { ac_status=$?; continue; }
- # Check for guested configure.
- if test -f "$ac_srcdir/configure.gnu"; then
- echo &&
- $SHELL "$ac_srcdir/configure.gnu" --help=recursive
- elif test -f "$ac_srcdir/configure"; then
- echo &&
- $SHELL "$ac_srcdir/configure" --help=recursive
- else
- $as_echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2
- fi || ac_status=$?
- cd "$ac_pwd" || { ac_status=$?; break; }
- done
-fi
-
-test -n "$ac_init_help" && exit $ac_status
-if $ac_init_version; then
- cat <<\_ACEOF
-ejabberd configure 3.0.0-alpha-x
-generated by GNU Autoconf 2.65
-
-Copyright (C) 2009 Free Software Foundation, Inc.
-This configure script is free software; the Free Software Foundation
-gives unlimited permission to copy, distribute and modify it.
-_ACEOF
- exit
-fi
-
-## ------------------------ ##
-## Autoconf initialization. ##
-## ------------------------ ##
-
-# ac_fn_c_try_compile LINENO
-# --------------------------
-# Try to compile conftest.$ac_ext, and return whether this succeeded.
-ac_fn_c_try_compile ()
-{
- as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
- rm -f conftest.$ac_objext
- if { { ac_try="$ac_compile"
-case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_compile") 2>conftest.err
- ac_status=$?
- if test -s conftest.err; then
- grep -v '^ *+' conftest.err >conftest.er1
- cat conftest.er1 >&5
- mv -f conftest.er1 conftest.err
- fi
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; } && {
- test -z "$ac_c_werror_flag" ||
- test ! -s conftest.err
- } && test -s conftest.$ac_objext; then :
- ac_retval=0
-else
- $as_echo "$as_me: failed program was:" >&5
-sed 's/^/| /' conftest.$ac_ext >&5
-
- ac_retval=1
-fi
- eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;}
- as_fn_set_status $ac_retval
-
-} # ac_fn_c_try_compile
-
-# ac_fn_c_try_cpp LINENO
-# ----------------------
-# Try to preprocess conftest.$ac_ext, and return whether this succeeded.
-ac_fn_c_try_cpp ()
-{
- as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
- if { { ac_try="$ac_cpp conftest.$ac_ext"
-case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_cpp conftest.$ac_ext") 2>conftest.err
- ac_status=$?
- if test -s conftest.err; then
- grep -v '^ *+' conftest.err >conftest.er1
- cat conftest.er1 >&5
- mv -f conftest.er1 conftest.err
- fi
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; } >/dev/null && {
- test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" ||
- test ! -s conftest.err
- }; then :
- ac_retval=0
-else
- $as_echo "$as_me: failed program was:" >&5
-sed 's/^/| /' conftest.$ac_ext >&5
-
- ac_retval=1
-fi
- eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;}
- as_fn_set_status $ac_retval
-
-} # ac_fn_c_try_cpp
-
-# ac_fn_c_try_run LINENO
-# ----------------------
-# Try to link conftest.$ac_ext, and return whether this succeeded. Assumes
-# that executables *can* be run.
-ac_fn_c_try_run ()
-{
- as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
- if { { ac_try="$ac_link"
-case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_link") 2>&5
- ac_status=$?
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; } && { ac_try='./conftest$ac_exeext'
- { { case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_try") 2>&5
- ac_status=$?
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; }; }; then :
- ac_retval=0
-else
- $as_echo "$as_me: program exited with status $ac_status" >&5
- $as_echo "$as_me: failed program was:" >&5
-sed 's/^/| /' conftest.$ac_ext >&5
-
- ac_retval=$ac_status
-fi
- rm -rf conftest.dSYM conftest_ipa8_conftest.oo
- eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;}
- as_fn_set_status $ac_retval
-
-} # ac_fn_c_try_run
-
-# ac_fn_c_check_header_mongrel LINENO HEADER VAR INCLUDES
-# -------------------------------------------------------
-# Tests whether HEADER exists, giving a warning if it cannot be compiled using
-# the include files in INCLUDES and setting the cache variable VAR
-# accordingly.
-ac_fn_c_check_header_mongrel ()
-{
- as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
- if { as_var=$3; eval "test \"\${$as_var+set}\" = set"; }; then :
- { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
-$as_echo_n "checking for $2... " >&6; }
-if { as_var=$3; eval "test \"\${$as_var+set}\" = set"; }; then :
- $as_echo_n "(cached) " >&6
-fi
-eval ac_res=\$$3
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
-$as_echo "$ac_res" >&6; }
-else
- # Is the header compilable?
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking $2 usability" >&5
-$as_echo_n "checking $2 usability... " >&6; }
-cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-$4
-#include <$2>
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
- ac_header_compiler=yes
-else
- ac_header_compiler=no
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_header_compiler" >&5
-$as_echo "$ac_header_compiler" >&6; }
-
-# Is the header present?
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking $2 presence" >&5
-$as_echo_n "checking $2 presence... " >&6; }
-cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include <$2>
-_ACEOF
-if ac_fn_c_try_cpp "$LINENO"; then :
- ac_header_preproc=yes
-else
- ac_header_preproc=no
-fi
-rm -f conftest.err conftest.$ac_ext
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_header_preproc" >&5
-$as_echo "$ac_header_preproc" >&6; }
-
-# So? What about this header?
-case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in #((
- yes:no: )
- { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: accepted by the compiler, rejected by the preprocessor!" >&5
-$as_echo "$as_me: WARNING: $2: accepted by the compiler, rejected by the preprocessor!" >&2;}
- { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5
-$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;}
- ;;
- no:yes:* )
- { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: present but cannot be compiled" >&5
-$as_echo "$as_me: WARNING: $2: present but cannot be compiled" >&2;}
- { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: check for missing prerequisite headers?" >&5
-$as_echo "$as_me: WARNING: $2: check for missing prerequisite headers?" >&2;}
- { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: see the Autoconf documentation" >&5
-$as_echo "$as_me: WARNING: $2: see the Autoconf documentation" >&2;}
- { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: section \"Present But Cannot Be Compiled\"" >&5
-$as_echo "$as_me: WARNING: $2: section \"Present But Cannot Be Compiled\"" >&2;}
- { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5
-$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;}
-( cat <<\_ASBOX
-## --------------------------------------- ##
-## Report this to ejabberd@process-one.net ##
-## --------------------------------------- ##
-_ASBOX
- ) | sed "s/^/$as_me: WARNING: /" >&2
- ;;
-esac
- { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
-$as_echo_n "checking for $2... " >&6; }
-if { as_var=$3; eval "test \"\${$as_var+set}\" = set"; }; then :
- $as_echo_n "(cached) " >&6
-else
- eval "$3=\$ac_header_compiler"
-fi
-eval ac_res=\$$3
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
-$as_echo "$ac_res" >&6; }
-fi
- eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;}
-
-} # ac_fn_c_check_header_mongrel
-
-# ac_fn_c_check_header_compile LINENO HEADER VAR INCLUDES
-# -------------------------------------------------------
-# Tests whether HEADER exists and can be compiled using the include files in
-# INCLUDES, setting the cache variable VAR accordingly.
-ac_fn_c_check_header_compile ()
-{
- as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
- { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
-$as_echo_n "checking for $2... " >&6; }
-if { as_var=$3; eval "test \"\${$as_var+set}\" = set"; }; then :
- $as_echo_n "(cached) " >&6
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-$4
-#include <$2>
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
- eval "$3=yes"
-else
- eval "$3=no"
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
-fi
-eval ac_res=\$$3
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
-$as_echo "$ac_res" >&6; }
- eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;}
-
-} # ac_fn_c_check_header_compile
-
-# ac_fn_c_try_link LINENO
-# -----------------------
-# Try to link conftest.$ac_ext, and return whether this succeeded.
-ac_fn_c_try_link ()
-{
- as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
- rm -f conftest.$ac_objext conftest$ac_exeext
- if { { ac_try="$ac_link"
-case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_link") 2>conftest.err
- ac_status=$?
- if test -s conftest.err; then
- grep -v '^ *+' conftest.err >conftest.er1
- cat conftest.er1 >&5
- mv -f conftest.er1 conftest.err
- fi
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; } && {
- test -z "$ac_c_werror_flag" ||
- test ! -s conftest.err
- } && test -s conftest$ac_exeext && {
- test "$cross_compiling" = yes ||
- $as_test_x conftest$ac_exeext
- }; then :
- ac_retval=0
-else
- $as_echo "$as_me: failed program was:" >&5
-sed 's/^/| /' conftest.$ac_ext >&5
-
- ac_retval=1
-fi
- # Delete the IPA/IPO (Inter Procedural Analysis/Optimization) information
- # created by the PGI compiler (conftest_ipa8_conftest.oo), as it would
- # interfere with the next link command; also delete a directory that is
- # left behind by Apple's compiler. We do this before executing the actions.
- rm -rf conftest.dSYM conftest_ipa8_conftest.oo
- eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;}
- as_fn_set_status $ac_retval
-
-} # ac_fn_c_try_link
-
-# ac_fn_erl_try_run LINENO
-# ------------------------
-# Try to link conftest.$ac_ext, and return whether this succeeded. Assumes
-# that executables *can* be run.
-ac_fn_erl_try_run ()
-{
- as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
- if { { ac_try="$ac_link"
-case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_link") 2>&5
- ac_status=$?
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; } && { ac_try='./conftest$ac_exeext'
- { { case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_try") 2>&5
- ac_status=$?
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; }; }; then :
- ac_retval=0
-else
- $as_echo "$as_me: program exited with status $ac_status" >&5
- $as_echo "$as_me: failed program was:" >&5
-sed 's/^/| /' conftest.$ac_ext >&5
-
- ac_retval=$ac_status
-fi
- rm -rf conftest.dSYM conftest_ipa8_conftest.oo
- eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;}
- as_fn_set_status $ac_retval
-
-} # ac_fn_erl_try_run
-cat >config.log <<_ACEOF
-This file contains any messages produced by compilers while
-running configure, to aid debugging if configure makes a mistake.
-
-It was created by ejabberd $as_me 3.0.0-alpha-x, which was
-generated by GNU Autoconf 2.65. Invocation command line was
-
- $ $0 $@
-
-_ACEOF
-exec 5>>config.log
-{
-cat <<_ASUNAME
-## --------- ##
-## Platform. ##
-## --------- ##
-
-hostname = `(hostname || uname -n) 2>/dev/null | sed 1q`
-uname -m = `(uname -m) 2>/dev/null || echo unknown`
-uname -r = `(uname -r) 2>/dev/null || echo unknown`
-uname -s = `(uname -s) 2>/dev/null || echo unknown`
-uname -v = `(uname -v) 2>/dev/null || echo unknown`
-
-/usr/bin/uname -p = `(/usr/bin/uname -p) 2>/dev/null || echo unknown`
-/bin/uname -X = `(/bin/uname -X) 2>/dev/null || echo unknown`
-
-/bin/arch = `(/bin/arch) 2>/dev/null || echo unknown`
-/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null || echo unknown`
-/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null || echo unknown`
-/usr/bin/hostinfo = `(/usr/bin/hostinfo) 2>/dev/null || echo unknown`
-/bin/machine = `(/bin/machine) 2>/dev/null || echo unknown`
-/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null || echo unknown`
-/bin/universe = `(/bin/universe) 2>/dev/null || echo unknown`
-
-_ASUNAME
-
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- $as_echo "PATH: $as_dir"
- done
-IFS=$as_save_IFS
-
-} >&5
-
-cat >&5 <<_ACEOF
-
-
-## ----------- ##
-## Core tests. ##
-## ----------- ##
-
-_ACEOF
-
-
-# Keep a trace of the command line.
-# Strip out --no-create and --no-recursion so they do not pile up.
-# Strip out --silent because we don't want to record it for future runs.
-# Also quote any args containing shell meta-characters.
-# Make two passes to allow for proper duplicate-argument suppression.
-ac_configure_args=
-ac_configure_args0=
-ac_configure_args1=
-ac_must_keep_next=false
-for ac_pass in 1 2
-do
- for ac_arg
- do
- case $ac_arg in
- -no-create | --no-c* | -n | -no-recursion | --no-r*) continue ;;
- -q | -quiet | --quiet | --quie | --qui | --qu | --q \
- | -silent | --silent | --silen | --sile | --sil)
- continue ;;
- *\'*)
- ac_arg=`$as_echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;;
- esac
- case $ac_pass in
- 1) as_fn_append ac_configure_args0 " '$ac_arg'" ;;
- 2)
- as_fn_append ac_configure_args1 " '$ac_arg'"
- if test $ac_must_keep_next = true; then
- ac_must_keep_next=false # Got value, back to normal.
- else
- case $ac_arg in
- *=* | --config-cache | -C | -disable-* | --disable-* \
- | -enable-* | --enable-* | -gas | --g* | -nfp | --nf* \
- | -q | -quiet | --q* | -silent | --sil* | -v | -verb* \
- | -with-* | --with-* | -without-* | --without-* | --x)
- case "$ac_configure_args0 " in
- "$ac_configure_args1"*" '$ac_arg' "* ) continue ;;
- esac
- ;;
- -* ) ac_must_keep_next=true ;;
- esac
- fi
- as_fn_append ac_configure_args " '$ac_arg'"
- ;;
- esac
- done
-done
-{ ac_configure_args0=; unset ac_configure_args0;}
-{ ac_configure_args1=; unset ac_configure_args1;}
-
-# When interrupted or exit'd, cleanup temporary files, and complete
-# config.log. We remove comments because anyway the quotes in there
-# would cause problems or look ugly.
-# WARNING: Use '\'' to represent an apostrophe within the trap.
-# WARNING: Do not start the trap code with a newline, due to a FreeBSD 4.0 bug.
-trap 'exit_status=$?
- # Save into config.log some information that might help in debugging.
- {
- echo
-
- cat <<\_ASBOX
-## ---------------- ##
-## Cache variables. ##
-## ---------------- ##
-_ASBOX
- echo
- # The following way of writing the cache mishandles newlines in values,
-(
- for ac_var in `(set) 2>&1 | sed -n '\''s/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'\''`; do
- eval ac_val=\$$ac_var
- case $ac_val in #(
- *${as_nl}*)
- case $ac_var in #(
- *_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5
-$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;;
- esac
- case $ac_var in #(
- _ | IFS | as_nl) ;; #(
- BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #(
- *) { eval $ac_var=; unset $ac_var;} ;;
- esac ;;
- esac
- done
- (set) 2>&1 |
- case $as_nl`(ac_space='\'' '\''; set) 2>&1` in #(
- *${as_nl}ac_space=\ *)
- sed -n \
- "s/'\''/'\''\\\\'\'''\''/g;
- s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\''\\2'\''/p"
- ;; #(
- *)
- sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
- ;;
- esac |
- sort
-)
- echo
-
- cat <<\_ASBOX
-## ----------------- ##
-## Output variables. ##
-## ----------------- ##
-_ASBOX
- echo
- for ac_var in $ac_subst_vars
- do
- eval ac_val=\$$ac_var
- case $ac_val in
- *\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
- esac
- $as_echo "$ac_var='\''$ac_val'\''"
- done | sort
- echo
-
- if test -n "$ac_subst_files"; then
- cat <<\_ASBOX
-## ------------------- ##
-## File substitutions. ##
-## ------------------- ##
-_ASBOX
- echo
- for ac_var in $ac_subst_files
- do
- eval ac_val=\$$ac_var
- case $ac_val in
- *\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
- esac
- $as_echo "$ac_var='\''$ac_val'\''"
- done | sort
- echo
- fi
-
- if test -s confdefs.h; then
- cat <<\_ASBOX
-## ----------- ##
-## confdefs.h. ##
-## ----------- ##
-_ASBOX
- echo
- cat confdefs.h
- echo
- fi
- test "$ac_signal" != 0 &&
- $as_echo "$as_me: caught signal $ac_signal"
- $as_echo "$as_me: exit $exit_status"
- } >&5
- rm -f core *.core core.conftest.* &&
- rm -f -r conftest* confdefs* conf$$* $ac_clean_files &&
- exit $exit_status
-' 0
-for ac_signal in 1 2 13 15; do
- trap 'ac_signal='$ac_signal'; as_fn_exit 1' $ac_signal
-done
-ac_signal=0
-
-# confdefs.h avoids OS command line length limits that DEFS can exceed.
-rm -f -r conftest* confdefs.h
-
-$as_echo "/* confdefs.h */" > confdefs.h
-
-# Predefined preprocessor variables.
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_NAME "$PACKAGE_NAME"
-_ACEOF
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_TARNAME "$PACKAGE_TARNAME"
-_ACEOF
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_VERSION "$PACKAGE_VERSION"
-_ACEOF
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_STRING "$PACKAGE_STRING"
-_ACEOF
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_BUGREPORT "$PACKAGE_BUGREPORT"
-_ACEOF
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_URL "$PACKAGE_URL"
-_ACEOF
-
-
-# Let the site file select an alternate cache file if it wants to.
-# Prefer an explicitly selected file to automatically selected ones.
-ac_site_file1=NONE
-ac_site_file2=NONE
-if test -n "$CONFIG_SITE"; then
- ac_site_file1=$CONFIG_SITE
-elif test "x$prefix" != xNONE; then
- ac_site_file1=$prefix/share/config.site
- ac_site_file2=$prefix/etc/config.site
-else
- ac_site_file1=$ac_default_prefix/share/config.site
- ac_site_file2=$ac_default_prefix/etc/config.site
-fi
-for ac_site_file in "$ac_site_file1" "$ac_site_file2"
-do
- test "x$ac_site_file" = xNONE && continue
- if test /dev/null != "$ac_site_file" && test -r "$ac_site_file"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: loading site script $ac_site_file" >&5
-$as_echo "$as_me: loading site script $ac_site_file" >&6;}
- sed 's/^/| /' "$ac_site_file" >&5
- . "$ac_site_file"
- fi
-done
-
-if test -r "$cache_file"; then
- # Some versions of bash will fail to source /dev/null (special files
- # actually), so we avoid doing that. DJGPP emulates it as a regular file.
- if test /dev/null != "$cache_file" && test -f "$cache_file"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: loading cache $cache_file" >&5
-$as_echo "$as_me: loading cache $cache_file" >&6;}
- case $cache_file in
- [\\/]* | ?:[\\/]* ) . "$cache_file";;
- *) . "./$cache_file";;
- esac
- fi
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: creating cache $cache_file" >&5
-$as_echo "$as_me: creating cache $cache_file" >&6;}
- >$cache_file
-fi
-
-# Check that the precious variables saved in the cache have kept the same
-# value.
-ac_cache_corrupted=false
-for ac_var in $ac_precious_vars; do
- eval ac_old_set=\$ac_cv_env_${ac_var}_set
- eval ac_new_set=\$ac_env_${ac_var}_set
- eval ac_old_val=\$ac_cv_env_${ac_var}_value
- eval ac_new_val=\$ac_env_${ac_var}_value
- case $ac_old_set,$ac_new_set in
- set,)
- { $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5
-$as_echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;}
- ac_cache_corrupted=: ;;
- ,set)
- { $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was not set in the previous run" >&5
-$as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;}
- ac_cache_corrupted=: ;;
- ,);;
- *)
- if test "x$ac_old_val" != "x$ac_new_val"; then
- # differences in whitespace do not lead to failure.
- ac_old_val_w=`echo x $ac_old_val`
- ac_new_val_w=`echo x $ac_new_val`
- if test "$ac_old_val_w" != "$ac_new_val_w"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' has changed since the previous run:" >&5
-$as_echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;}
- ac_cache_corrupted=:
- else
- { $as_echo "$as_me:${as_lineno-$LINENO}: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&5
-$as_echo "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;}
- eval $ac_var=\$ac_old_val
- fi
- { $as_echo "$as_me:${as_lineno-$LINENO}: former value: \`$ac_old_val'" >&5
-$as_echo "$as_me: former value: \`$ac_old_val'" >&2;}
- { $as_echo "$as_me:${as_lineno-$LINENO}: current value: \`$ac_new_val'" >&5
-$as_echo "$as_me: current value: \`$ac_new_val'" >&2;}
- fi;;
- esac
- # Pass precious variables to config.status.
- if test "$ac_new_set" = set; then
- case $ac_new_val in
- *\'*) ac_arg=$ac_var=`$as_echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;;
- *) ac_arg=$ac_var=$ac_new_val ;;
- esac
- case " $ac_configure_args " in
- *" '$ac_arg' "*) ;; # Avoid dups. Use of quotes ensures accuracy.
- *) as_fn_append ac_configure_args " '$ac_arg'" ;;
- esac
- fi
-done
-if $ac_cache_corrupted; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
-$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
- { $as_echo "$as_me:${as_lineno-$LINENO}: error: changes in the environment can compromise the build" >&5
-$as_echo "$as_me: error: changes in the environment can compromise the build" >&2;}
- as_fn_error "run \`make distclean' and/or \`rm $cache_file' and start over" "$LINENO" 5
-fi
-## -------------------- ##
-## Main body of script. ##
-## -------------------- ##
-
-ac_ext=c
-ac_cpp='$CPP $CPPFLAGS'
-ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
-ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
-ac_compiler_gnu=$ac_cv_c_compiler_gnu
-
-
-
-# Checks for programs.
-ac_ext=c
-ac_cpp='$CPP $CPPFLAGS'
-ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
-ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
-ac_compiler_gnu=$ac_cv_c_compiler_gnu
-if test -n "$ac_tool_prefix"; then
- # Extract the first word of "${ac_tool_prefix}gcc", so it can be a program name with args.
-set dummy ${ac_tool_prefix}gcc; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_prog_CC+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- if test -n "$CC"; then
- ac_cv_prog_CC="$CC" # Let the user override the test.
-else
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_prog_CC="${ac_tool_prefix}gcc"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
-fi
-fi
-CC=$ac_cv_prog_CC
-if test -n "$CC"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
-$as_echo "$CC" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
-
-fi
-if test -z "$ac_cv_prog_CC"; then
- ac_ct_CC=$CC
- # Extract the first word of "gcc", so it can be a program name with args.
-set dummy gcc; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_prog_ac_ct_CC+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- if test -n "$ac_ct_CC"; then
- ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
-else
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_prog_ac_ct_CC="gcc"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
-fi
-fi
-ac_ct_CC=$ac_cv_prog_ac_ct_CC
-if test -n "$ac_ct_CC"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_CC" >&5
-$as_echo "$ac_ct_CC" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
- if test "x$ac_ct_CC" = x; then
- CC=""
- else
- case $cross_compiling:$ac_tool_warned in
-yes:)
-{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
-$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
-ac_tool_warned=yes ;;
-esac
- CC=$ac_ct_CC
- fi
-else
- CC="$ac_cv_prog_CC"
-fi
-
-if test -z "$CC"; then
- if test -n "$ac_tool_prefix"; then
- # Extract the first word of "${ac_tool_prefix}cc", so it can be a program name with args.
-set dummy ${ac_tool_prefix}cc; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_prog_CC+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- if test -n "$CC"; then
- ac_cv_prog_CC="$CC" # Let the user override the test.
-else
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_prog_CC="${ac_tool_prefix}cc"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
-fi
-fi
-CC=$ac_cv_prog_CC
-if test -n "$CC"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
-$as_echo "$CC" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
-
- fi
-fi
-if test -z "$CC"; then
- # Extract the first word of "cc", so it can be a program name with args.
-set dummy cc; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_prog_CC+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- if test -n "$CC"; then
- ac_cv_prog_CC="$CC" # Let the user override the test.
-else
- ac_prog_rejected=no
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- if test "$as_dir/$ac_word$ac_exec_ext" = "/usr/ucb/cc"; then
- ac_prog_rejected=yes
- continue
- fi
- ac_cv_prog_CC="cc"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
-if test $ac_prog_rejected = yes; then
- # We found a bogon in the path, so make sure we never use it.
- set dummy $ac_cv_prog_CC
- shift
- if test $# != 0; then
- # We chose a different compiler from the bogus one.
- # However, it has the same basename, so the bogon will be chosen
- # first if we set CC to just the basename; use the full file name.
- shift
- ac_cv_prog_CC="$as_dir/$ac_word${1+' '}$@"
- fi
-fi
-fi
-fi
-CC=$ac_cv_prog_CC
-if test -n "$CC"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
-$as_echo "$CC" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
-
-fi
-if test -z "$CC"; then
- if test -n "$ac_tool_prefix"; then
- for ac_prog in cl.exe
- do
- # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args.
-set dummy $ac_tool_prefix$ac_prog; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_prog_CC+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- if test -n "$CC"; then
- ac_cv_prog_CC="$CC" # Let the user override the test.
-else
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_prog_CC="$ac_tool_prefix$ac_prog"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
-fi
-fi
-CC=$ac_cv_prog_CC
-if test -n "$CC"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
-$as_echo "$CC" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
-
- test -n "$CC" && break
- done
-fi
-if test -z "$CC"; then
- ac_ct_CC=$CC
- for ac_prog in cl.exe
-do
- # Extract the first word of "$ac_prog", so it can be a program name with args.
-set dummy $ac_prog; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_prog_ac_ct_CC+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- if test -n "$ac_ct_CC"; then
- ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
-else
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_prog_ac_ct_CC="$ac_prog"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
-fi
-fi
-ac_ct_CC=$ac_cv_prog_ac_ct_CC
-if test -n "$ac_ct_CC"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_CC" >&5
-$as_echo "$ac_ct_CC" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
-
- test -n "$ac_ct_CC" && break
-done
-
- if test "x$ac_ct_CC" = x; then
- CC=""
- else
- case $cross_compiling:$ac_tool_warned in
-yes:)
-{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
-$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
-ac_tool_warned=yes ;;
-esac
- CC=$ac_ct_CC
- fi
-fi
-
-fi
-
-
-test -z "$CC" && { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
-$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
-as_fn_error "no acceptable C compiler found in \$PATH
-See \`config.log' for more details." "$LINENO" 5; }
-
-# Provide some information about the compiler.
-$as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler version" >&5
-set X $ac_compile
-ac_compiler=$2
-for ac_option in --version -v -V -qversion; do
- { { ac_try="$ac_compiler $ac_option >&5"
-case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_compiler $ac_option >&5") 2>conftest.err
- ac_status=$?
- if test -s conftest.err; then
- sed '10a\
-... rest of stderr output deleted ...
- 10q' conftest.err >conftest.er1
- cat conftest.er1 >&5
- fi
- rm -f conftest.er1 conftest.err
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; }
-done
-
-cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-
-int
-main ()
-{
-
- ;
- return 0;
-}
-_ACEOF
-ac_clean_files_save=$ac_clean_files
-ac_clean_files="$ac_clean_files a.out a.out.dSYM a.exe b.out"
-# Try to create an executable without -o first, disregard a.out.
-# It will help us diagnose broken compilers, and finding out an intuition
-# of exeext.
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the C compiler works" >&5
-$as_echo_n "checking whether the C compiler works... " >&6; }
-ac_link_default=`$as_echo "$ac_link" | sed 's/ -o *conftest[^ ]*//'`
-
-# The possible output files:
-ac_files="a.out conftest.exe conftest a.exe a_out.exe b.out conftest.*"
-
-ac_rmfiles=
-for ac_file in $ac_files
-do
- case $ac_file in
- *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;;
- * ) ac_rmfiles="$ac_rmfiles $ac_file";;
- esac
-done
-rm -f $ac_rmfiles
-
-if { { ac_try="$ac_link_default"
-case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_link_default") 2>&5
- ac_status=$?
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; }; then :
- # Autoconf-2.13 could set the ac_cv_exeext variable to `no'.
-# So ignore a value of `no', otherwise this would lead to `EXEEXT = no'
-# in a Makefile. We should not override ac_cv_exeext if it was cached,
-# so that the user can short-circuit this test for compilers unknown to
-# Autoconf.
-for ac_file in $ac_files ''
-do
- test -f "$ac_file" || continue
- case $ac_file in
- *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj )
- ;;
- [ab].out )
- # We found the default executable, but exeext='' is most
- # certainly right.
- break;;
- *.* )
- if test "${ac_cv_exeext+set}" = set && test "$ac_cv_exeext" != no;
- then :; else
- ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
- fi
- # We set ac_cv_exeext here because the later test for it is not
- # safe: cross compilers may not add the suffix if given an `-o'
- # argument, so we may need to know it at that point already.
- # Even if this section looks crufty: it has the advantage of
- # actually working.
- break;;
- * )
- break;;
- esac
-done
-test "$ac_cv_exeext" = no && ac_cv_exeext=
-
-else
- ac_file=''
-fi
-if test -z "$ac_file"; then :
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-$as_echo "$as_me: failed program was:" >&5
-sed 's/^/| /' conftest.$ac_ext >&5
-
-{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
-$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
-{ as_fn_set_status 77
-as_fn_error "C compiler cannot create executables
-See \`config.log' for more details." "$LINENO" 5; }; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
-$as_echo "yes" >&6; }
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler default output file name" >&5
-$as_echo_n "checking for C compiler default output file name... " >&6; }
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_file" >&5
-$as_echo "$ac_file" >&6; }
-ac_exeext=$ac_cv_exeext
-
-rm -f -r a.out a.out.dSYM a.exe conftest$ac_cv_exeext b.out
-ac_clean_files=$ac_clean_files_save
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for suffix of executables" >&5
-$as_echo_n "checking for suffix of executables... " >&6; }
-if { { ac_try="$ac_link"
-case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_link") 2>&5
- ac_status=$?
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; }; then :
- # If both `conftest.exe' and `conftest' are `present' (well, observable)
-# catch `conftest.exe'. For instance with Cygwin, `ls conftest' will
-# work properly (i.e., refer to `conftest.exe'), while it won't with
-# `rm'.
-for ac_file in conftest.exe conftest conftest.*; do
- test -f "$ac_file" || continue
- case $ac_file in
- *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;;
- *.* ) ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
- break;;
- * ) break;;
- esac
-done
-else
- { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
-$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
-as_fn_error "cannot compute suffix of executables: cannot compile and link
-See \`config.log' for more details." "$LINENO" 5; }
-fi
-rm -f conftest conftest$ac_cv_exeext
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_exeext" >&5
-$as_echo "$ac_cv_exeext" >&6; }
-
-rm -f conftest.$ac_ext
-EXEEXT=$ac_cv_exeext
-ac_exeext=$EXEEXT
-cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-int
-main ()
-{
-FILE *f = fopen ("conftest.out", "w");
- return ferror (f) || fclose (f) != 0;
-
- ;
- return 0;
-}
-_ACEOF
-ac_clean_files="$ac_clean_files conftest.out"
-# Check that the compiler produces executables we can run. If not, either
-# the compiler is broken, or we cross compile.
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are cross compiling" >&5
-$as_echo_n "checking whether we are cross compiling... " >&6; }
-if test "$cross_compiling" != yes; then
- { { ac_try="$ac_link"
-case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_link") 2>&5
- ac_status=$?
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; }
- if { ac_try='./conftest$ac_cv_exeext'
- { { case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_try") 2>&5
- ac_status=$?
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; }; }; then
- cross_compiling=no
- else
- if test "$cross_compiling" = maybe; then
- cross_compiling=yes
- else
- { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
-$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
-as_fn_error "cannot run C compiled programs.
-If you meant to cross compile, use \`--host'.
-See \`config.log' for more details." "$LINENO" 5; }
- fi
- fi
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $cross_compiling" >&5
-$as_echo "$cross_compiling" >&6; }
-
-rm -f conftest.$ac_ext conftest$ac_cv_exeext conftest.out
-ac_clean_files=$ac_clean_files_save
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for suffix of object files" >&5
-$as_echo_n "checking for suffix of object files... " >&6; }
-if test "${ac_cv_objext+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-
-int
-main ()
-{
-
- ;
- return 0;
-}
-_ACEOF
-rm -f conftest.o conftest.obj
-if { { ac_try="$ac_compile"
-case "(($ac_try" in
- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
- *) ac_try_echo=$ac_try;;
-esac
-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
-$as_echo "$ac_try_echo"; } >&5
- (eval "$ac_compile") 2>&5
- ac_status=$?
- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
- test $ac_status = 0; }; then :
- for ac_file in conftest.o conftest.obj conftest.*; do
- test -f "$ac_file" || continue;
- case $ac_file in
- *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM ) ;;
- *) ac_cv_objext=`expr "$ac_file" : '.*\.\(.*\)'`
- break;;
- esac
-done
-else
- $as_echo "$as_me: failed program was:" >&5
-sed 's/^/| /' conftest.$ac_ext >&5
-
-{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
-$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
-as_fn_error "cannot compute suffix of object files: cannot compile
-See \`config.log' for more details." "$LINENO" 5; }
-fi
-rm -f conftest.$ac_cv_objext conftest.$ac_ext
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_objext" >&5
-$as_echo "$ac_cv_objext" >&6; }
-OBJEXT=$ac_cv_objext
-ac_objext=$OBJEXT
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are using the GNU C compiler" >&5
-$as_echo_n "checking whether we are using the GNU C compiler... " >&6; }
-if test "${ac_cv_c_compiler_gnu+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-
-int
-main ()
-{
-#ifndef __GNUC__
- choke me
-#endif
-
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
- ac_compiler_gnu=yes
-else
- ac_compiler_gnu=no
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
-ac_cv_c_compiler_gnu=$ac_compiler_gnu
-
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_c_compiler_gnu" >&5
-$as_echo "$ac_cv_c_compiler_gnu" >&6; }
-if test $ac_compiler_gnu = yes; then
- GCC=yes
-else
- GCC=
-fi
-ac_test_CFLAGS=${CFLAGS+set}
-ac_save_CFLAGS=$CFLAGS
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CC accepts -g" >&5
-$as_echo_n "checking whether $CC accepts -g... " >&6; }
-if test "${ac_cv_prog_cc_g+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- ac_save_c_werror_flag=$ac_c_werror_flag
- ac_c_werror_flag=yes
- ac_cv_prog_cc_g=no
- CFLAGS="-g"
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-
-int
-main ()
-{
-
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
- ac_cv_prog_cc_g=yes
-else
- CFLAGS=""
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-
-int
-main ()
-{
-
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
-
-else
- ac_c_werror_flag=$ac_save_c_werror_flag
- CFLAGS="-g"
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-
-int
-main ()
-{
-
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
- ac_cv_prog_cc_g=yes
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
- ac_c_werror_flag=$ac_save_c_werror_flag
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_g" >&5
-$as_echo "$ac_cv_prog_cc_g" >&6; }
-if test "$ac_test_CFLAGS" = set; then
- CFLAGS=$ac_save_CFLAGS
-elif test $ac_cv_prog_cc_g = yes; then
- if test "$GCC" = yes; then
- CFLAGS="-g -O2"
- else
- CFLAGS="-g"
- fi
-else
- if test "$GCC" = yes; then
- CFLAGS="-O2"
- else
- CFLAGS=
- fi
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $CC option to accept ISO C89" >&5
-$as_echo_n "checking for $CC option to accept ISO C89... " >&6; }
-if test "${ac_cv_prog_cc_c89+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- ac_cv_prog_cc_c89=no
-ac_save_CC=$CC
-cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-#include
-#include
-#include
-/* Most of the following tests are stolen from RCS 5.7's src/conf.sh. */
-struct buf { int x; };
-FILE * (*rcsopen) (struct buf *, struct stat *, int);
-static char *e (p, i)
- char **p;
- int i;
-{
- return p[i];
-}
-static char *f (char * (*g) (char **, int), char **p, ...)
-{
- char *s;
- va_list v;
- va_start (v,p);
- s = g (p, va_arg (v,int));
- va_end (v);
- return s;
-}
-
-/* OSF 4.0 Compaq cc is some sort of almost-ANSI by default. It has
- function prototypes and stuff, but not '\xHH' hex character constants.
- These don't provoke an error unfortunately, instead are silently treated
- as 'x'. The following induces an error, until -std is added to get
- proper ANSI mode. Curiously '\x00'!='x' always comes out true, for an
- array size at least. It's necessary to write '\x00'==0 to get something
- that's true only with -std. */
-int osf4_cc_array ['\x00' == 0 ? 1 : -1];
-
-/* IBM C 6 for AIX is almost-ANSI by default, but it replaces macro parameters
- inside strings and character constants. */
-#define FOO(x) 'x'
-int xlc6_cc_array[FOO(a) == 'x' ? 1 : -1];
-
-int test (int i, double x);
-struct s1 {int (*f) (int a);};
-struct s2 {int (*f) (double a);};
-int pairnames (int, char **, FILE *(*)(struct buf *, struct stat *, int), int, int);
-int argc;
-char **argv;
-int
-main ()
-{
-return f (e, argv, 0) != argv[0] || f (e, argv, 1) != argv[1];
- ;
- return 0;
-}
-_ACEOF
-for ac_arg in '' -qlanglvl=extc89 -qlanglvl=ansi -std \
- -Ae "-Aa -D_HPUX_SOURCE" "-Xc -D__EXTENSIONS__"
-do
- CC="$ac_save_CC $ac_arg"
- if ac_fn_c_try_compile "$LINENO"; then :
- ac_cv_prog_cc_c89=$ac_arg
-fi
-rm -f core conftest.err conftest.$ac_objext
- test "x$ac_cv_prog_cc_c89" != "xno" && break
-done
-rm -f conftest.$ac_ext
-CC=$ac_save_CC
-
-fi
-# AC_CACHE_VAL
-case "x$ac_cv_prog_cc_c89" in
- x)
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: none needed" >&5
-$as_echo "none needed" >&6; } ;;
- xno)
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5
-$as_echo "unsupported" >&6; } ;;
- *)
- CC="$CC $ac_cv_prog_cc_c89"
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c89" >&5
-$as_echo "$ac_cv_prog_cc_c89" >&6; } ;;
-esac
-if test "x$ac_cv_prog_cc_c89" != xno; then :
-
-fi
-
-ac_ext=c
-ac_cpp='$CPP $CPPFLAGS'
-ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
-ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
-ac_compiler_gnu=$ac_cv_c_compiler_gnu
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether ${MAKE-make} sets \$(MAKE)" >&5
-$as_echo_n "checking whether ${MAKE-make} sets \$(MAKE)... " >&6; }
-set x ${MAKE-make}
-ac_make=`$as_echo "$2" | sed 's/+/p/g; s/[^a-zA-Z0-9_]/_/g'`
-if { as_var=ac_cv_prog_make_${ac_make}_set; eval "test \"\${$as_var+set}\" = set"; }; then :
- $as_echo_n "(cached) " >&6
-else
- cat >conftest.make <<\_ACEOF
-SHELL = /bin/sh
-all:
- @echo '@@@%%%=$(MAKE)=@@@%%%'
-_ACEOF
-# GNU make sometimes prints "make[1]: Entering...", which would confuse us.
-case `${MAKE-make} -f conftest.make 2>/dev/null` in
- *@@@%%%=?*=@@@%%%*)
- eval ac_cv_prog_make_${ac_make}_set=yes;;
- *)
- eval ac_cv_prog_make_${ac_make}_set=no;;
-esac
-rm -f conftest.make
-fi
-if eval test \$ac_cv_prog_make_${ac_make}_set = yes; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
-$as_echo "yes" >&6; }
- SET_MAKE=
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
- SET_MAKE="MAKE=${MAKE-make}"
-fi
-
-
-if test "x$GCC" = "xyes"; then
- CFLAGS="$CFLAGS -Wall"
-fi
-
-#locating erlang
-
-# Check whether --with-erlang was given.
-if test "${with_erlang+set}" = set; then :
- withval=$with_erlang;
-fi
-
-
- if test -n "$ac_tool_prefix"; then
- # Extract the first word of "${ac_tool_prefix}erlc", so it can be a program name with args.
-set dummy ${ac_tool_prefix}erlc; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_path_ERLC+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- case $ERLC in
- [\\/]* | ?:[\\/]*)
- ac_cv_path_ERLC="$ERLC" # Let the user override the test with a path.
- ;;
- *)
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-as_dummy="$with_erlang:$with_erlang/bin:$PATH"
-for as_dir in $as_dummy
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_path_ERLC="$as_dir/$ac_word$ac_exec_ext"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
- ;;
-esac
-fi
-ERLC=$ac_cv_path_ERLC
-if test -n "$ERLC"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ERLC" >&5
-$as_echo "$ERLC" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
-
-fi
-if test -z "$ac_cv_path_ERLC"; then
- ac_pt_ERLC=$ERLC
- # Extract the first word of "erlc", so it can be a program name with args.
-set dummy erlc; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_path_ac_pt_ERLC+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- case $ac_pt_ERLC in
- [\\/]* | ?:[\\/]*)
- ac_cv_path_ac_pt_ERLC="$ac_pt_ERLC" # Let the user override the test with a path.
- ;;
- *)
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-as_dummy="$with_erlang:$with_erlang/bin:$PATH"
-for as_dir in $as_dummy
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_path_ac_pt_ERLC="$as_dir/$ac_word$ac_exec_ext"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
- ;;
-esac
-fi
-ac_pt_ERLC=$ac_cv_path_ac_pt_ERLC
-if test -n "$ac_pt_ERLC"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_pt_ERLC" >&5
-$as_echo "$ac_pt_ERLC" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
- if test "x$ac_pt_ERLC" = x; then
- ERLC=""
- else
- case $cross_compiling:$ac_tool_warned in
-yes:)
-{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
-$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
-ac_tool_warned=yes ;;
-esac
- ERLC=$ac_pt_ERLC
- fi
-else
- ERLC="$ac_cv_path_ERLC"
-fi
-
- if test -n "$ac_tool_prefix"; then
- # Extract the first word of "${ac_tool_prefix}erl", so it can be a program name with args.
-set dummy ${ac_tool_prefix}erl; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_path_ERL+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- case $ERL in
- [\\/]* | ?:[\\/]*)
- ac_cv_path_ERL="$ERL" # Let the user override the test with a path.
- ;;
- *)
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-as_dummy="$with_erlang:$with_erlang/bin:$PATH"
-for as_dir in $as_dummy
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_path_ERL="$as_dir/$ac_word$ac_exec_ext"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
- ;;
-esac
-fi
-ERL=$ac_cv_path_ERL
-if test -n "$ERL"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ERL" >&5
-$as_echo "$ERL" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
-
-fi
-if test -z "$ac_cv_path_ERL"; then
- ac_pt_ERL=$ERL
- # Extract the first word of "erl", so it can be a program name with args.
-set dummy erl; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_path_ac_pt_ERL+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- case $ac_pt_ERL in
- [\\/]* | ?:[\\/]*)
- ac_cv_path_ac_pt_ERL="$ac_pt_ERL" # Let the user override the test with a path.
- ;;
- *)
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-as_dummy="$with_erlang:$with_erlang/bin:$PATH"
-for as_dir in $as_dummy
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_path_ac_pt_ERL="$as_dir/$ac_word$ac_exec_ext"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
- ;;
-esac
-fi
-ac_pt_ERL=$ac_cv_path_ac_pt_ERL
-if test -n "$ac_pt_ERL"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_pt_ERL" >&5
-$as_echo "$ac_pt_ERL" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
- if test "x$ac_pt_ERL" = x; then
- ERL=""
- else
- case $cross_compiling:$ac_tool_warned in
-yes:)
-{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
-$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
-ac_tool_warned=yes ;;
-esac
- ERL=$ac_pt_ERL
- fi
-else
- ERL="$ac_cv_path_ERL"
-fi
-
-
- if test "z$ERLC" = "z" || test "z$ERL" = "z"; then
- as_fn_error "erlang not found" "$LINENO" 5
- fi
-
-
- cat >>conftest.erl <<_EOF
-
--module(conftest).
--author('alexey@sevcom.net').
-
--export([start/0]).
-
-start() ->
- EIDirS = code:lib_dir("erl_interface") ++ "\n",
- EILibS = libpath("erl_interface") ++ "\n",
- EXMPPDir = code:lib_dir("exmpp"),
- case EXMPPDir of
- {error, bad_name} -> exit("exmpp not found");
- _ -> ok
- end,
- EXMPPDirS = EXMPPDir ++ "\n",
- RootDirS = code:root_dir() ++ "\n",
- file:write_file("conftest.out", list_to_binary(EIDirS ++ EILibS ++ EXMPPDirS ++ RootDirS)),
- halt().
-
-%% return physical architecture based on OS/Processor
-archname() ->
- ArchStr = erlang:system_info(system_architecture),
- case os:type() of
- {win32, _} -> "windows";
- {unix,UnixName} ->
- Specs = string:tokens(ArchStr,"-"),
- Cpu = case lists:nth(2,Specs) of
- "pc" -> "x86";
- _ -> hd(Specs)
- end,
- atom_to_list(UnixName) ++ "-" ++ Cpu;
- _ -> "generic"
- end.
-
-%% Return arch-based library path or a default value if this directory
-%% does not exist
-libpath(App) ->
- PrivDir = code:priv_dir(App),
- ArchDir = archname(),
- LibArchDir = filename:join([PrivDir,"lib",ArchDir]),
- case file:list_dir(LibArchDir) of
- %% Arch lib dir exists: We use it
- {ok, _List} -> LibArchDir;
- %% Arch lib dir does not exist: Return the default value
- %% ({error, enoent}):
- _Error -> code:lib_dir("erl_interface") ++ "/lib"
- end.
-
-_EOF
-
- if ! $ERLC conftest.erl; then
- as_fn_error "could not compile sample program" "$LINENO" 5
- fi
-
- if ! $ERL -s conftest -noshell; then
- as_fn_error "could not run sample program" "$LINENO" 5
- fi
-
- if ! test -f conftest.out; then
- as_fn_error "erlang program was not properly executed, (conftest.out was not produced)" "$LINENO" 5
- fi
-
- # First line
- ERLANG_EI_DIR=`cat conftest.out | head -n 1`
- # Second line
- ERLANG_EI_LIB=`cat conftest.out | head -n 2 | tail -n 1`
- # Third line
- ERLANG_EXMPP=`cat conftest.out | head -n 3 | tail -n 1`
- # End line
- ERLANG_DIR=`cat conftest.out | tail -n 1`
-
- ERLANG_CFLAGS="-I$ERLANG_EI_DIR/include -I$ERLANG_DIR/usr/include"
- ERLANG_LIBS="-L$ERLANG_EI_LIB -lerl_interface -lei"
-
-
-
-
-
-
-
-
-# Checks for typedefs, structures, and compiler characteristics.
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for an ANSI C-conforming const" >&5
-$as_echo_n "checking for an ANSI C-conforming const... " >&6; }
-if test "${ac_cv_c_const+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-
-int
-main ()
-{
-/* FIXME: Include the comments suggested by Paul. */
-#ifndef __cplusplus
- /* Ultrix mips cc rejects this. */
- typedef int charset[2];
- const charset cs;
- /* SunOS 4.1.1 cc rejects this. */
- char const *const *pcpcc;
- char **ppc;
- /* NEC SVR4.0.2 mips cc rejects this. */
- struct point {int x, y;};
- static struct point const zero = {0,0};
- /* AIX XL C 1.02.0.0 rejects this.
- It does not let you subtract one const X* pointer from another in
- an arm of an if-expression whose if-part is not a constant
- expression */
- const char *g = "string";
- pcpcc = &g + (g ? g-g : 0);
- /* HPUX 7.0 cc rejects these. */
- ++pcpcc;
- ppc = (char**) pcpcc;
- pcpcc = (char const *const *) ppc;
- { /* SCO 3.2v4 cc rejects this. */
- char *t;
- char const *s = 0 ? (char *) 0 : (char const *) 0;
-
- *t++ = 0;
- if (s) return 0;
- }
- { /* Someone thinks the Sun supposedly-ANSI compiler will reject this. */
- int x[] = {25, 17};
- const int *foo = &x[0];
- ++foo;
- }
- { /* Sun SC1.0 ANSI compiler rejects this -- but not the above. */
- typedef const int *iptr;
- iptr p = 0;
- ++p;
- }
- { /* AIX XL C 1.02.0.0 rejects this saying
- "k.c", line 2.27: 1506-025 (S) Operand must be a modifiable lvalue. */
- struct s { int j; const int *ap[3]; };
- struct s *b; b->j = 5;
- }
- { /* ULTRIX-32 V3.1 (Rev 9) vcc rejects this */
- const int foo = 10;
- if (!foo) return 0;
- }
- return !cs[0] && !zero.x;
-#endif
-
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
- ac_cv_c_const=yes
-else
- ac_cv_c_const=no
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_c_const" >&5
-$as_echo "$ac_cv_c_const" >&6; }
-if test $ac_cv_c_const = no; then
-
-$as_echo "#define const /**/" >>confdefs.h
-
-fi
-
-
-# Check Erlang headers are installed
-#AC_CHECK_HEADER(erl_driver.h,,[AC_MSG_ERROR([cannot find Erlang header files])])
-
-# Change default prefix
-
-
-# Checks for library functions.
-ac_ext=c
-ac_cpp='$CPP $CPPFLAGS'
-ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
-ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
-ac_compiler_gnu=$ac_cv_c_compiler_gnu
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking how to run the C preprocessor" >&5
-$as_echo_n "checking how to run the C preprocessor... " >&6; }
-# On Suns, sometimes $CPP names a directory.
-if test -n "$CPP" && test -d "$CPP"; then
- CPP=
-fi
-if test -z "$CPP"; then
- if test "${ac_cv_prog_CPP+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- # Double quotes because CPP needs to be expanded
- for CPP in "$CC -E" "$CC -E -traditional-cpp" "/lib/cpp"
- do
- ac_preproc_ok=false
-for ac_c_preproc_warn_flag in '' yes
-do
- # Use a header file that comes with gcc, so configuring glibc
- # with a fresh cross-compiler works.
- # Prefer to if __STDC__ is defined, since
- # exists even on freestanding compilers.
- # On the NeXT, cc -E runs the code through the compiler's parser,
- # not just through cpp. "Syntax error" is here to catch this case.
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#ifdef __STDC__
-# include
-#else
-# include
-#endif
- Syntax error
-_ACEOF
-if ac_fn_c_try_cpp "$LINENO"; then :
-
-else
- # Broken: fails on valid input.
-continue
-fi
-rm -f conftest.err conftest.$ac_ext
-
- # OK, works on sane cases. Now check whether nonexistent headers
- # can be detected and how.
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-_ACEOF
-if ac_fn_c_try_cpp "$LINENO"; then :
- # Broken: success on invalid input.
-continue
-else
- # Passes both tests.
-ac_preproc_ok=:
-break
-fi
-rm -f conftest.err conftest.$ac_ext
-
-done
-# Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped.
-rm -f conftest.err conftest.$ac_ext
-if $ac_preproc_ok; then :
- break
-fi
-
- done
- ac_cv_prog_CPP=$CPP
-
-fi
- CPP=$ac_cv_prog_CPP
-else
- ac_cv_prog_CPP=$CPP
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CPP" >&5
-$as_echo "$CPP" >&6; }
-ac_preproc_ok=false
-for ac_c_preproc_warn_flag in '' yes
-do
- # Use a header file that comes with gcc, so configuring glibc
- # with a fresh cross-compiler works.
- # Prefer to if __STDC__ is defined, since
- # exists even on freestanding compilers.
- # On the NeXT, cc -E runs the code through the compiler's parser,
- # not just through cpp. "Syntax error" is here to catch this case.
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#ifdef __STDC__
-# include
-#else
-# include
-#endif
- Syntax error
-_ACEOF
-if ac_fn_c_try_cpp "$LINENO"; then :
-
-else
- # Broken: fails on valid input.
-continue
-fi
-rm -f conftest.err conftest.$ac_ext
-
- # OK, works on sane cases. Now check whether nonexistent headers
- # can be detected and how.
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-_ACEOF
-if ac_fn_c_try_cpp "$LINENO"; then :
- # Broken: success on invalid input.
-continue
-else
- # Passes both tests.
-ac_preproc_ok=:
-break
-fi
-rm -f conftest.err conftest.$ac_ext
-
-done
-# Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped.
-rm -f conftest.err conftest.$ac_ext
-if $ac_preproc_ok; then :
-
-else
- { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
-$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
-as_fn_error "C preprocessor \"$CPP\" fails sanity check
-See \`config.log' for more details." "$LINENO" 5; }
-fi
-
-ac_ext=c
-ac_cpp='$CPP $CPPFLAGS'
-ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
-ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
-ac_compiler_gnu=$ac_cv_c_compiler_gnu
-
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for grep that handles long lines and -e" >&5
-$as_echo_n "checking for grep that handles long lines and -e... " >&6; }
-if test "${ac_cv_path_GREP+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- if test -z "$GREP"; then
- ac_path_GREP_found=false
- # Loop through the user's path and test for each of PROGNAME-LIST
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH$PATH_SEPARATOR/usr/xpg4/bin
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_prog in grep ggrep; do
- for ac_exec_ext in '' $ac_executable_extensions; do
- ac_path_GREP="$as_dir/$ac_prog$ac_exec_ext"
- { test -f "$ac_path_GREP" && $as_test_x "$ac_path_GREP"; } || continue
-# Check for GNU ac_path_GREP and select it if it is found.
- # Check for GNU $ac_path_GREP
-case `"$ac_path_GREP" --version 2>&1` in
-*GNU*)
- ac_cv_path_GREP="$ac_path_GREP" ac_path_GREP_found=:;;
-*)
- ac_count=0
- $as_echo_n 0123456789 >"conftest.in"
- while :
- do
- cat "conftest.in" "conftest.in" >"conftest.tmp"
- mv "conftest.tmp" "conftest.in"
- cp "conftest.in" "conftest.nl"
- $as_echo 'GREP' >> "conftest.nl"
- "$ac_path_GREP" -e 'GREP$' -e '-(cannot match)-' < "conftest.nl" >"conftest.out" 2>/dev/null || break
- diff "conftest.out" "conftest.nl" >/dev/null 2>&1 || break
- as_fn_arith $ac_count + 1 && ac_count=$as_val
- if test $ac_count -gt ${ac_path_GREP_max-0}; then
- # Best one so far, save it but keep looking for a better one
- ac_cv_path_GREP="$ac_path_GREP"
- ac_path_GREP_max=$ac_count
- fi
- # 10*(2^10) chars as input seems more than enough
- test $ac_count -gt 10 && break
- done
- rm -f conftest.in conftest.tmp conftest.nl conftest.out;;
-esac
-
- $ac_path_GREP_found && break 3
- done
- done
- done
-IFS=$as_save_IFS
- if test -z "$ac_cv_path_GREP"; then
- as_fn_error "no acceptable grep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5
- fi
-else
- ac_cv_path_GREP=$GREP
-fi
-
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_path_GREP" >&5
-$as_echo "$ac_cv_path_GREP" >&6; }
- GREP="$ac_cv_path_GREP"
-
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for egrep" >&5
-$as_echo_n "checking for egrep... " >&6; }
-if test "${ac_cv_path_EGREP+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- if echo a | $GREP -E '(a|b)' >/dev/null 2>&1
- then ac_cv_path_EGREP="$GREP -E"
- else
- if test -z "$EGREP"; then
- ac_path_EGREP_found=false
- # Loop through the user's path and test for each of PROGNAME-LIST
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH$PATH_SEPARATOR/usr/xpg4/bin
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_prog in egrep; do
- for ac_exec_ext in '' $ac_executable_extensions; do
- ac_path_EGREP="$as_dir/$ac_prog$ac_exec_ext"
- { test -f "$ac_path_EGREP" && $as_test_x "$ac_path_EGREP"; } || continue
-# Check for GNU ac_path_EGREP and select it if it is found.
- # Check for GNU $ac_path_EGREP
-case `"$ac_path_EGREP" --version 2>&1` in
-*GNU*)
- ac_cv_path_EGREP="$ac_path_EGREP" ac_path_EGREP_found=:;;
-*)
- ac_count=0
- $as_echo_n 0123456789 >"conftest.in"
- while :
- do
- cat "conftest.in" "conftest.in" >"conftest.tmp"
- mv "conftest.tmp" "conftest.in"
- cp "conftest.in" "conftest.nl"
- $as_echo 'EGREP' >> "conftest.nl"
- "$ac_path_EGREP" 'EGREP$' < "conftest.nl" >"conftest.out" 2>/dev/null || break
- diff "conftest.out" "conftest.nl" >/dev/null 2>&1 || break
- as_fn_arith $ac_count + 1 && ac_count=$as_val
- if test $ac_count -gt ${ac_path_EGREP_max-0}; then
- # Best one so far, save it but keep looking for a better one
- ac_cv_path_EGREP="$ac_path_EGREP"
- ac_path_EGREP_max=$ac_count
- fi
- # 10*(2^10) chars as input seems more than enough
- test $ac_count -gt 10 && break
- done
- rm -f conftest.in conftest.tmp conftest.nl conftest.out;;
-esac
-
- $ac_path_EGREP_found && break 3
- done
- done
- done
-IFS=$as_save_IFS
- if test -z "$ac_cv_path_EGREP"; then
- as_fn_error "no acceptable egrep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5
- fi
-else
- ac_cv_path_EGREP=$EGREP
-fi
-
- fi
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_path_EGREP" >&5
-$as_echo "$ac_cv_path_EGREP" >&6; }
- EGREP="$ac_cv_path_EGREP"
-
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for ANSI C header files" >&5
-$as_echo_n "checking for ANSI C header files... " >&6; }
-if test "${ac_cv_header_stdc+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-#include
-#include
-#include
-
-int
-main ()
-{
-
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
- ac_cv_header_stdc=yes
-else
- ac_cv_header_stdc=no
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
-
-if test $ac_cv_header_stdc = yes; then
- # SunOS 4.x string.h does not declare mem*, contrary to ANSI.
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-
-_ACEOF
-if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
- $EGREP "memchr" >/dev/null 2>&1; then :
-
-else
- ac_cv_header_stdc=no
-fi
-rm -f conftest*
-
-fi
-
-if test $ac_cv_header_stdc = yes; then
- # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-
-_ACEOF
-if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
- $EGREP "free" >/dev/null 2>&1; then :
-
-else
- ac_cv_header_stdc=no
-fi
-rm -f conftest*
-
-fi
-
-if test $ac_cv_header_stdc = yes; then
- # /bin/cc in Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi.
- if test "$cross_compiling" = yes; then :
- :
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-#include
-#if ((' ' & 0x0FF) == 0x020)
-# define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
-# define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c))
-#else
-# define ISLOWER(c) \
- (('a' <= (c) && (c) <= 'i') \
- || ('j' <= (c) && (c) <= 'r') \
- || ('s' <= (c) && (c) <= 'z'))
-# define TOUPPER(c) (ISLOWER(c) ? ((c) | 0x40) : (c))
-#endif
-
-#define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
-int
-main ()
-{
- int i;
- for (i = 0; i < 256; i++)
- if (XOR (islower (i), ISLOWER (i))
- || toupper (i) != TOUPPER (i))
- return 2;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_run "$LINENO"; then :
-
-else
- ac_cv_header_stdc=no
-fi
-rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
- conftest.$ac_objext conftest.beam conftest.$ac_ext
-fi
-
-fi
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_header_stdc" >&5
-$as_echo "$ac_cv_header_stdc" >&6; }
-if test $ac_cv_header_stdc = yes; then
-
-$as_echo "#define STDC_HEADERS 1" >>confdefs.h
-
-fi
-
-# On IRIX 5.3, sys/types and inttypes.h are conflicting.
-for ac_header in sys/types.h sys/stat.h stdlib.h string.h memory.h strings.h \
- inttypes.h stdint.h unistd.h
-do :
- as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh`
-ac_fn_c_check_header_compile "$LINENO" "$ac_header" "$as_ac_Header" "$ac_includes_default
-"
-eval as_val=\$$as_ac_Header
- if test "x$as_val" = x""yes; then :
- cat >>confdefs.h <<_ACEOF
-#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1
-_ACEOF
-
-fi
-
-done
-
-
-for ac_header in stdlib.h
-do :
- ac_fn_c_check_header_mongrel "$LINENO" "stdlib.h" "ac_cv_header_stdlib_h" "$ac_includes_default"
-if test "x$ac_cv_header_stdlib_h" = x""yes; then :
- cat >>confdefs.h <<_ACEOF
-#define HAVE_STDLIB_H 1
-_ACEOF
-
-fi
-
-done
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for GNU libc compatible malloc" >&5
-$as_echo_n "checking for GNU libc compatible malloc... " >&6; }
-if test "${ac_cv_func_malloc_0_nonnull+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- if test "$cross_compiling" = yes; then :
- ac_cv_func_malloc_0_nonnull=no
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#if defined STDC_HEADERS || defined HAVE_STDLIB_H
-# include
-#else
-char *malloc ();
-#endif
-
-int
-main ()
-{
-return ! malloc (0);
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_run "$LINENO"; then :
- ac_cv_func_malloc_0_nonnull=yes
-else
- ac_cv_func_malloc_0_nonnull=no
-fi
-rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
- conftest.$ac_objext conftest.beam conftest.$ac_ext
-fi
-
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_func_malloc_0_nonnull" >&5
-$as_echo "$ac_cv_func_malloc_0_nonnull" >&6; }
-if test $ac_cv_func_malloc_0_nonnull = yes; then :
-
-$as_echo "#define HAVE_MALLOC 1" >>confdefs.h
-
-else
- $as_echo "#define HAVE_MALLOC 0" >>confdefs.h
-
- case " $LIBOBJS " in
- *" malloc.$ac_objext "* ) ;;
- *) LIBOBJS="$LIBOBJS malloc.$ac_objext"
- ;;
-esac
-
-
-$as_echo "#define malloc rpl_malloc" >>confdefs.h
-
-fi
-
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for ANSI C header files" >&5
-$as_echo_n "checking for ANSI C header files... " >&6; }
-if test "${ac_cv_header_stdc+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-#include
-#include
-#include
-
-int
-main ()
-{
-
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
- ac_cv_header_stdc=yes
-else
- ac_cv_header_stdc=no
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
-
-if test $ac_cv_header_stdc = yes; then
- # SunOS 4.x string.h does not declare mem*, contrary to ANSI.
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-
-_ACEOF
-if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
- $EGREP "memchr" >/dev/null 2>&1; then :
-
-else
- ac_cv_header_stdc=no
-fi
-rm -f conftest*
-
-fi
-
-if test $ac_cv_header_stdc = yes; then
- # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-
-_ACEOF
-if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
- $EGREP "free" >/dev/null 2>&1; then :
-
-else
- ac_cv_header_stdc=no
-fi
-rm -f conftest*
-
-fi
-
-if test $ac_cv_header_stdc = yes; then
- # /bin/cc in Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi.
- if test "$cross_compiling" = yes; then :
- :
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-#include
-#if ((' ' & 0x0FF) == 0x020)
-# define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
-# define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c))
-#else
-# define ISLOWER(c) \
- (('a' <= (c) && (c) <= 'i') \
- || ('j' <= (c) && (c) <= 'r') \
- || ('s' <= (c) && (c) <= 'z'))
-# define TOUPPER(c) (ISLOWER(c) ? ((c) | 0x40) : (c))
-#endif
-
-#define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
-int
-main ()
-{
- int i;
- for (i = 0; i < 256; i++)
- if (XOR (islower (i), ISLOWER (i))
- || toupper (i) != TOUPPER (i))
- return 2;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_run "$LINENO"; then :
-
-else
- ac_cv_header_stdc=no
-fi
-rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
- conftest.$ac_objext conftest.beam conftest.$ac_ext
-fi
-
-fi
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_header_stdc" >&5
-$as_echo "$ac_cv_header_stdc" >&6; }
-if test $ac_cv_header_stdc = yes; then
-
-$as_echo "#define STDC_HEADERS 1" >>confdefs.h
-
-fi
-
-
-
-mod_muc=
-make_mod_muc=
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether build mod_muc" >&5
-$as_echo_n "checking whether build mod_muc... " >&6; }
-# Check whether --enable-mod_muc was given.
-if test "${enable_mod_muc+set}" = set; then :
- enableval=$enable_mod_muc; mr_enable_mod_muc="$enableval"
-else
- mr_enable_mod_muc=yes
-fi
-
-if test "$mr_enable_mod_muc" = "yes"; then
-mod_muc=mod_muc
-make_mod_muc=mod_muc/Makefile
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $mr_enable_mod_muc" >&5
-$as_echo "$mr_enable_mod_muc" >&6; }
-
-
-
-
-
-mod_proxy65=
-make_mod_proxy65=
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether build mod_proxy65" >&5
-$as_echo_n "checking whether build mod_proxy65... " >&6; }
-# Check whether --enable-mod_proxy65 was given.
-if test "${enable_mod_proxy65+set}" = set; then :
- enableval=$enable_mod_proxy65; mr_enable_mod_proxy65="$enableval"
-else
- mr_enable_mod_proxy65=yes
-fi
-
-if test "$mr_enable_mod_proxy65" = "yes"; then
-mod_proxy65=mod_proxy65
-make_mod_proxy65=mod_proxy65/Makefile
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $mr_enable_mod_proxy65" >&5
-$as_echo "$mr_enable_mod_proxy65" >&6; }
-
-
-
-
-
-mod_pubsub=
-make_mod_pubsub=
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether build mod_pubsub" >&5
-$as_echo_n "checking whether build mod_pubsub... " >&6; }
-# Check whether --enable-mod_pubsub was given.
-if test "${enable_mod_pubsub+set}" = set; then :
- enableval=$enable_mod_pubsub; mr_enable_mod_pubsub="$enableval"
-else
- mr_enable_mod_pubsub=yes
-fi
-
-if test "$mr_enable_mod_pubsub" = "yes"; then
-mod_pubsub=mod_pubsub
-make_mod_pubsub=mod_pubsub/Makefile
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $mr_enable_mod_pubsub" >&5
-$as_echo "$mr_enable_mod_pubsub" >&6; }
-
-
-
-
-
-eldap=
-make_eldap=
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether build eldap" >&5
-$as_echo_n "checking whether build eldap... " >&6; }
-# Check whether --enable-eldap was given.
-if test "${enable_eldap+set}" = set; then :
- enableval=$enable_eldap; mr_enable_eldap="$enableval"
-else
- mr_enable_eldap=yes
-fi
-
-if test "$mr_enable_eldap" = "yes"; then
-eldap=eldap
-make_eldap=eldap/Makefile
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $mr_enable_eldap" >&5
-$as_echo "$mr_enable_eldap" >&6; }
-
-
-
-
-
-odbc=
-make_odbc=
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether build odbc" >&5
-$as_echo_n "checking whether build odbc... " >&6; }
-# Check whether --enable-odbc was given.
-if test "${enable_odbc+set}" = set; then :
- enableval=$enable_odbc; mr_enable_odbc="$enableval"
-else
- mr_enable_odbc=no
-fi
-
-if test "$mr_enable_odbc" = "yes"; then
-odbc=odbc
-make_odbc=odbc/Makefile
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $mr_enable_odbc" >&5
-$as_echo "$mr_enable_odbc" >&6; }
-
-
-
-
-
-tls=
-make_tls=
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether build tls" >&5
-$as_echo_n "checking whether build tls... " >&6; }
-# Check whether --enable-tls was given.
-if test "${enable_tls+set}" = set; then :
- enableval=$enable_tls; mr_enable_tls="$enableval"
-else
- mr_enable_tls=yes
-fi
-
-if test "$mr_enable_tls" = "yes"; then
-tls=tls
-make_tls=tls/Makefile
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $mr_enable_tls" >&5
-$as_echo "$mr_enable_tls" >&6; }
-
-
-
-
-
-web=
-make_web=
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether build web" >&5
-$as_echo_n "checking whether build web... " >&6; }
-# Check whether --enable-web was given.
-if test "${enable_web+set}" = set; then :
- enableval=$enable_web; mr_enable_web="$enableval"
-else
- mr_enable_web=yes
-fi
-
-if test "$mr_enable_web" = "yes"; then
-web=web
-make_web=web/Makefile
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $mr_enable_web" >&5
-$as_echo "$mr_enable_web" >&6; }
-
-
-
-
-
-
-ejabberd_zlib=
-make_ejabberd_zlib=
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether build ejabberd_zlib" >&5
-$as_echo_n "checking whether build ejabberd_zlib... " >&6; }
-# Check whether --enable-ejabberd_zlib was given.
-if test "${enable_ejabberd_zlib+set}" = set; then :
- enableval=$enable_ejabberd_zlib; mr_enable_ejabberd_zlib="$enableval"
-else
- mr_enable_ejabberd_zlib=yes
-fi
-
-if test "$mr_enable_ejabberd_zlib" = "yes"; then
-ejabberd_zlib=ejabberd_zlib
-make_ejabberd_zlib=ejabberd_zlib/Makefile
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $mr_enable_ejabberd_zlib" >&5
-$as_echo "$mr_enable_ejabberd_zlib" >&6; }
-
-
-
-
-#locating zlib
-
-# Check whether --with-zlib was given.
-if test "${with_zlib+set}" = set; then :
- withval=$with_zlib;
-fi
-
-
-if test x"$ejabberd_zlib" != x; then
- ZLIB_CFLAGS=
- ZLIB_LIBS=
- if test x"$with_zlib" != x; then
- ZLIB_CFLAGS="-I$with_zlib/include"
- ZLIB_LIBS="-L$with_zlib/lib"
- fi
-
- { $as_echo "$as_me:${as_lineno-$LINENO}: checking for gzgets in -lz" >&5
-$as_echo_n "checking for gzgets in -lz... " >&6; }
-if test "${ac_cv_lib_z_gzgets+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- ac_check_lib_save_LIBS=$LIBS
-LIBS="-lz "$ZLIB_LIBS" $LIBS"
-cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-
-/* Override any GCC internal prototype to avoid an error.
- Use char because int might match the return type of a GCC
- builtin and then its argument prototype would still apply. */
-#ifdef __cplusplus
-extern "C"
-#endif
-char gzgets ();
-int
-main ()
-{
-return gzgets ();
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_link "$LINENO"; then :
- ac_cv_lib_z_gzgets=yes
-else
- ac_cv_lib_z_gzgets=no
-fi
-rm -f core conftest.err conftest.$ac_objext \
- conftest$ac_exeext conftest.$ac_ext
-LIBS=$ac_check_lib_save_LIBS
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_z_gzgets" >&5
-$as_echo "$ac_cv_lib_z_gzgets" >&6; }
-if test "x$ac_cv_lib_z_gzgets" = x""yes; then :
- ZLIB_LIBS="$ZLIB_LIBS -lz"
- zlib_found=yes
-else
- zlib_found=no
-fi
-
- if test $zlib_found = no; then
- as_fn_error "Could not find development files of zlib library. Install them or disable \`ejabberd_zlib' with: --disable-ejabberd_zlib" "$LINENO" 5
- fi
- zlib_save_CFLAGS="$CFLAGS"
- CFLAGS="$CFLAGS $ZLIB_CFLAGS"
- zlib_save_CPPFLAGS="$CFLAGS"
- CPPFLAGS="$CPPFLAGS $ZLIB_CFLAGS"
- for ac_header in zlib.h
-do :
- ac_fn_c_check_header_mongrel "$LINENO" "zlib.h" "ac_cv_header_zlib_h" "$ac_includes_default"
-if test "x$ac_cv_header_zlib_h" = x""yes; then :
- cat >>confdefs.h <<_ACEOF
-#define HAVE_ZLIB_H 1
-_ACEOF
-
-else
- zlib_found=no
-fi
-
-done
-
- if test $zlib_found = no; then
- as_fn_error "Could not find zlib.h. Install it or disable \`ejabberd_zlib' with: --disable-ejabberd_zlib" "$LINENO" 5
- fi
- CFLAGS="$zlib_save_CFLAGS"
- CPPFLAGS="$zlib_save_CPPFLAGS"
-
-
-
-fi
-
-
-
-pam=
-make_pam=
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether build pam" >&5
-$as_echo_n "checking whether build pam... " >&6; }
-# Check whether --enable-pam was given.
-if test "${enable_pam+set}" = set; then :
- enableval=$enable_pam; mr_enable_pam="$enableval"
-else
- mr_enable_pam=no
-fi
-
-if test "$mr_enable_pam" = "yes"; then
-pam=pam
-make_pam=pam/Makefile
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $mr_enable_pam" >&5
-$as_echo "$mr_enable_pam" >&6; }
-
-
-
-
-#locating PAM
-
-# Check whether --with-pam was given.
-if test "${with_pam+set}" = set; then :
- withval=$with_pam;
-fi
-
-if test x"$pam" != x; then
- PAM_CFLAGS=
- PAM_LIBS=
- if test x"$with_pam" != x; then
- PAM_CFLAGS="-I$with_pam/include"
- PAM_LIBS="-L$with_pam/lib"
- fi
-
- { $as_echo "$as_me:${as_lineno-$LINENO}: checking for pam_start in -lpam" >&5
-$as_echo_n "checking for pam_start in -lpam... " >&6; }
-if test "${ac_cv_lib_pam_pam_start+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- ac_check_lib_save_LIBS=$LIBS
-LIBS="-lpam "$PAM_LIBS" $LIBS"
-cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-
-/* Override any GCC internal prototype to avoid an error.
- Use char because int might match the return type of a GCC
- builtin and then its argument prototype would still apply. */
-#ifdef __cplusplus
-extern "C"
-#endif
-char pam_start ();
-int
-main ()
-{
-return pam_start ();
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_link "$LINENO"; then :
- ac_cv_lib_pam_pam_start=yes
-else
- ac_cv_lib_pam_pam_start=no
-fi
-rm -f core conftest.err conftest.$ac_objext \
- conftest$ac_exeext conftest.$ac_ext
-LIBS=$ac_check_lib_save_LIBS
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_pam_pam_start" >&5
-$as_echo "$ac_cv_lib_pam_pam_start" >&6; }
-if test "x$ac_cv_lib_pam_pam_start" = x""yes; then :
- PAM_LIBS="$PAM_LIBS -lpam"
- pam_found=yes
-else
- pam_found=no
-fi
-
- if test $pam_found = no; then
- as_fn_error "Could not find development files of PAM library. Install them or disable \`pam' with: --disable-pam" "$LINENO" 5
- fi
- pam_save_CFLAGS="$CFLAGS"
- CFLAGS="$CFLAGS $PAM_CFLAGS"
- pam_save_CPPFLAGS="$CPPFLAGS"
- CPPFLAGS="$CPPFLAGS $PAM_CFLAGS"
- for ac_header in security/pam_appl.h
-do :
- ac_fn_c_check_header_mongrel "$LINENO" "security/pam_appl.h" "ac_cv_header_security_pam_appl_h" "$ac_includes_default"
-if test "x$ac_cv_header_security_pam_appl_h" = x""yes; then :
- cat >>confdefs.h <<_ACEOF
-#define HAVE_SECURITY_PAM_APPL_H 1
-_ACEOF
-
-else
- pam_found=no
-fi
-
-done
-
- if test $pam_found = no; then
- as_fn_error "Could not find security/pam_appl.h. Install it or disable \`pam' with: --disable-pam" "$LINENO" 5
- fi
- CFLAGS="$pam_save_CFLAGS"
- CPPFLAGS="$pam_save_CPPFLAGS"
-
-
-
-fi
-
-
-# Check whether --enable-hipe was given.
-if test "${enable_hipe+set}" = set; then :
- enableval=$enable_hipe; case "${enableval}" in
- yes) hipe=true ;;
- no) hipe=false ;;
- *) as_fn_error "bad value ${enableval} for --enable-hipe" "$LINENO" 5 ;;
-esac
-else
- hipe=false
-fi
-
-
-
-# Check whether --enable-roster_gateway_workaround was given.
-if test "${enable_roster_gateway_workaround+set}" = set; then :
- enableval=$enable_roster_gateway_workaround; case "${enableval}" in
- yes) roster_gateway_workaround=true ;;
- no) roster_gateway_workaround=false ;;
- *) as_fn_error "bad value ${enableval} for --enable-roster-gateway-workaround" "$LINENO" 5 ;;
-esac
-else
- roster_gateway_workaround=false
-fi
-
-
-
-# Check whether --enable-mssql was given.
-if test "${enable_mssql+set}" = set; then :
- enableval=$enable_mssql; case "${enableval}" in
- yes) db_type=mssql ;;
- no) db_type=generic ;;
- *) as_fn_error "bad value ${enableval} for --enable-mssql" "$LINENO" 5 ;;
-esac
-else
- db_type=generic
-fi
-
-
-
-# Check whether --enable-transient_supervisors was given.
-if test "${enable_transient_supervisors+set}" = set; then :
- enableval=$enable_transient_supervisors; case "${enableval}" in
- yes) transient_supervisors=true ;;
- no) transient_supervisors=false ;;
- *) as_fn_error "bad value ${enableval} for --enable-transient_supervisors" "$LINENO" 5 ;;
-esac
-else
- transient_supervisors=true
-fi
-
-
-
-# Check whether --enable-full_xml was given.
-if test "${enable_full_xml+set}" = set; then :
- enableval=$enable_full_xml; case "${enableval}" in
- yes) full_xml=true ;;
- no) full_xml=false ;;
- *) as_fn_error "bad value ${enableval} for --enable-full-xml" "$LINENO" 5 ;;
-esac
-else
- full_xml=false
-fi
-
-
-
-ac_config_files="$ac_config_files Makefile $make_mod_muc $make_mod_pubsub $make_mod_proxy65 $make_eldap $make_pam $make_web stun/Makefile $make_tls $make_odbc $make_ejabberd_zlib"
-
-#openssl
-
-# Check whether --with-openssl was given.
-if test "${with_openssl+set}" = set; then :
- withval=$with_openssl;
-fi
-
-unset SSL_LIBS;
-unset SSL_CFLAGS;
-have_openssl=no
-if test x"$tls" != x; then
- for ssl_prefix in $withval /usr/local/ssl /usr/lib/ssl /usr/ssl /usr/pkg /usr/local /usr; do
- printf "looking for openssl in $ssl_prefix...\n"
- SSL_CFLAGS="-I$ssl_prefix/include"
- SSL_LIBS="-L$ssl_prefix/lib -lcrypto"
- { $as_echo "$as_me:${as_lineno-$LINENO}: checking for SSL_new in -lssl" >&5
-$as_echo_n "checking for SSL_new in -lssl... " >&6; }
-if test "${ac_cv_lib_ssl_SSL_new+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- ac_check_lib_save_LIBS=$LIBS
-LIBS="-lssl $SSL_LIBS $SSL_CFLAGS $LIBS"
-cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-
-/* Override any GCC internal prototype to avoid an error.
- Use char because int might match the return type of a GCC
- builtin and then its argument prototype would still apply. */
-#ifdef __cplusplus
-extern "C"
-#endif
-char SSL_new ();
-int
-main ()
-{
-return SSL_new ();
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_link "$LINENO"; then :
- ac_cv_lib_ssl_SSL_new=yes
-else
- ac_cv_lib_ssl_SSL_new=no
-fi
-rm -f core conftest.err conftest.$ac_objext \
- conftest$ac_exeext conftest.$ac_ext
-LIBS=$ac_check_lib_save_LIBS
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_ssl_SSL_new" >&5
-$as_echo "$ac_cv_lib_ssl_SSL_new" >&6; }
-if test "x$ac_cv_lib_ssl_SSL_new" = x""yes; then :
- have_openssl=yes
-else
- have_openssl=no
-fi
-
- if test x"$have_openssl" = xyes; then
- save_CPPFLAGS=$CPPFLAGS
- CPPFLAGS="-I$ssl_prefix/include $CPPFLAGS"
- for ac_header in openssl/ssl.h
-do :
- ac_fn_c_check_header_mongrel "$LINENO" "openssl/ssl.h" "ac_cv_header_openssl_ssl_h" "$ac_includes_default"
-if test "x$ac_cv_header_openssl_ssl_h" = x""yes; then :
- cat >>confdefs.h <<_ACEOF
-#define HAVE_OPENSSL_SSL_H 1
-_ACEOF
- have_openssl_h=yes
-fi
-
-done
-
- CPPFLAGS=$save_CPPFLAGS
- if test x"$have_openssl_h" = xyes; then
- have_openssl=yes
- printf "openssl found in $ssl_prefix\n";
- SSL_LIBS="-L$ssl_prefix/lib -lssl -lcrypto"
- CPPFLAGS="-I$ssl_prefix/include $CPPFLAGS"
- SSL_CFLAGS="-DHAVE_SSL"
- break
- fi
- else
- # Clear this from the autoconf cache, so in the next pass of
- # this loop with different -L arguments, it will test again.
- unset ac_cv_lib_ssl_SSL_new
- fi
- done
-if test x${have_openssl} != xyes; then
- as_fn_error "Could not find development files of OpenSSL library. Install them or disable \`tls' with: --disable-tls" "$LINENO" 5
-fi
-
-
-fi
-
-# If ssl is kerberized it need krb5.h
-# On RedHat and OpenBSD, krb5.h is in an unsual place:
-KRB5_INCLUDE="`krb5-config --cflags 2>/dev/null`"
-if test -n "$KRB5_INCLUDE" ; then
- CPPFLAGS="$CPPFLAGS $KRB5_INCLUDE"
-else
- # For RedHat For BSD
- for D in /usr/kerberos/include /usr/include/kerberos /usr/include/kerberosV
- do
- if test -d $D ; then
- CPPFLAGS="$CPPFLAGS -I$D"
- fi
- done
-fi
-ac_fn_c_check_header_mongrel "$LINENO" "krb5.h" "ac_cv_header_krb5_h" "$ac_includes_default"
-if test "x$ac_cv_header_krb5_h" = x""yes; then :
-
-fi
-
-
-
-ENABLEUSER=""
-# Check whether --enable-user was given.
-if test "${enable_user+set}" = set; then :
- enableval=$enable_user; case "${enableval}" in
- yes) ENABLEUSER=`whoami` ;;
- no) ENABLEUSER="" ;;
- *) ENABLEUSER=$enableval
- esac
-fi
-
-if test "$ENABLEUSER" != ""; then
- echo "allow this system user to start ejabberd: $ENABLEUSER"
- INSTALLUSER=$ENABLEUSER
-
-fi
-
-ac_fn_c_check_header_mongrel "$LINENO" "openssl/md2.h" "ac_cv_header_openssl_md2_h" "$ac_includes_default"
-if test "x$ac_cv_header_openssl_md2_h" = x""yes; then :
- md2=true
-else
- md2=false
-fi
-
-
-
-
-ac_aux_dir=
-for ac_dir in "$srcdir" "$srcdir/.." "$srcdir/../.."; do
- for ac_t in install-sh install.sh shtool; do
- if test -f "$ac_dir/$ac_t"; then
- ac_aux_dir=$ac_dir
- ac_install_sh="$ac_aux_dir/$ac_t -c"
- break 2
- fi
- done
-done
-if test -z "$ac_aux_dir"; then
- as_fn_error "cannot find install-sh, install.sh, or shtool in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" "$LINENO" 5
-fi
-
-# These three variables are undocumented and unsupported,
-# and are intended to be withdrawn in a future Autoconf release.
-# They can cause serious problems if a builder's source tree is in a directory
-# whose full name contains unusual characters.
-ac_config_guess="$SHELL $ac_aux_dir/config.guess" # Please don't use this var.
-ac_config_sub="$SHELL $ac_aux_dir/config.sub" # Please don't use this var.
-ac_configure="$SHELL $ac_aux_dir/configure" # Please don't use this var.
-
-
-# Make sure we can run config.sub.
-$SHELL "$ac_aux_dir/config.sub" sun4 >/dev/null 2>&1 ||
- as_fn_error "cannot run $SHELL $ac_aux_dir/config.sub" "$LINENO" 5
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking build system type" >&5
-$as_echo_n "checking build system type... " >&6; }
-if test "${ac_cv_build+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- ac_build_alias=$build_alias
-test "x$ac_build_alias" = x &&
- ac_build_alias=`$SHELL "$ac_aux_dir/config.guess"`
-test "x$ac_build_alias" = x &&
- as_fn_error "cannot guess build type; you must specify one" "$LINENO" 5
-ac_cv_build=`$SHELL "$ac_aux_dir/config.sub" $ac_build_alias` ||
- as_fn_error "$SHELL $ac_aux_dir/config.sub $ac_build_alias failed" "$LINENO" 5
-
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_build" >&5
-$as_echo "$ac_cv_build" >&6; }
-case $ac_cv_build in
-*-*-*) ;;
-*) as_fn_error "invalid value of canonical build" "$LINENO" 5;;
-esac
-build=$ac_cv_build
-ac_save_IFS=$IFS; IFS='-'
-set x $ac_cv_build
-shift
-build_cpu=$1
-build_vendor=$2
-shift; shift
-# Remember, the first character of IFS is used to create $*,
-# except with old shells:
-build_os=$*
-IFS=$ac_save_IFS
-case $build_os in *\ *) build_os=`echo "$build_os" | sed 's/ /-/g'`;; esac
-
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking host system type" >&5
-$as_echo_n "checking host system type... " >&6; }
-if test "${ac_cv_host+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- if test "x$host_alias" = x; then
- ac_cv_host=$ac_cv_build
-else
- ac_cv_host=`$SHELL "$ac_aux_dir/config.sub" $host_alias` ||
- as_fn_error "$SHELL $ac_aux_dir/config.sub $host_alias failed" "$LINENO" 5
-fi
-
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_host" >&5
-$as_echo "$ac_cv_host" >&6; }
-case $ac_cv_host in
-*-*-*) ;;
-*) as_fn_error "invalid value of canonical host" "$LINENO" 5;;
-esac
-host=$ac_cv_host
-ac_save_IFS=$IFS; IFS='-'
-set x $ac_cv_host
-shift
-host_cpu=$1
-host_vendor=$2
-shift; shift
-# Remember, the first character of IFS is used to create $*,
-# except with old shells:
-host_os=$*
-IFS=$ac_save_IFS
-case $host_os in *\ *) host_os=`echo "$host_os" | sed 's/ /-/g'`;; esac
-
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking target system type" >&5
-$as_echo_n "checking target system type... " >&6; }
-if test "${ac_cv_target+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- if test "x$target_alias" = x; then
- ac_cv_target=$ac_cv_host
-else
- ac_cv_target=`$SHELL "$ac_aux_dir/config.sub" $target_alias` ||
- as_fn_error "$SHELL $ac_aux_dir/config.sub $target_alias failed" "$LINENO" 5
-fi
-
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_target" >&5
-$as_echo "$ac_cv_target" >&6; }
-case $ac_cv_target in
-*-*-*) ;;
-*) as_fn_error "invalid value of canonical target" "$LINENO" 5;;
-esac
-target=$ac_cv_target
-ac_save_IFS=$IFS; IFS='-'
-set x $ac_cv_target
-shift
-target_cpu=$1
-target_vendor=$2
-shift; shift
-# Remember, the first character of IFS is used to create $*,
-# except with old shells:
-target_os=$*
-IFS=$ac_save_IFS
-case $target_os in *\ *) target_os=`echo "$target_os" | sed 's/ /-/g'`;; esac
-
-
-# The aliases save the names the user supplied, while $host etc.
-# will get canonicalized.
-test -n "$target_alias" &&
- test "$program_prefix$program_suffix$program_transform_name" = \
- NONENONEs,x,x, &&
- program_prefix=${target_alias}-
-
-#AC_DEFINE_UNQUOTED(CPU_VENDOR_OS, "$target")
-#AC_SUBST(target_os)
-
-
-case "$target_os" in
- *darwin10*)
- echo "Target OS is 'Darwin10'"
- ac_ext=erl
-ac_compile='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext >&5'
-ac_link='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext >&5 && echo "#!/bin/sh" > conftest$ac_exeext && $as_echo "\"$ERL\" -run conftest start -run init stop -noshell" >> conftest$ac_exeext && chmod +x conftest$ac_exeext'
-
- if test -n "$ERLC"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: checking for erlc" >&5
-$as_echo_n "checking for erlc... " >&6; }
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ERLC" >&5
-$as_echo "$ERLC" >&6; }
-else
- if test -n "$ac_tool_prefix"; then
- # Extract the first word of "${ac_tool_prefix}erlc", so it can be a program name with args.
-set dummy ${ac_tool_prefix}erlc; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_path_ERLC+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- case $ERLC in
- [\\/]* | ?:[\\/]*)
- ac_cv_path_ERLC="$ERLC" # Let the user override the test with a path.
- ;;
- *)
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_path_ERLC="$as_dir/$ac_word$ac_exec_ext"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
- ;;
-esac
-fi
-ERLC=$ac_cv_path_ERLC
-if test -n "$ERLC"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ERLC" >&5
-$as_echo "$ERLC" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
-
-fi
-if test -z "$ac_cv_path_ERLC"; then
- ac_pt_ERLC=$ERLC
- # Extract the first word of "erlc", so it can be a program name with args.
-set dummy erlc; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if test "${ac_cv_path_ac_pt_ERLC+set}" = set; then :
- $as_echo_n "(cached) " >&6
-else
- case $ac_pt_ERLC in
- [\\/]* | ?:[\\/]*)
- ac_cv_path_ac_pt_ERLC="$ac_pt_ERLC" # Let the user override the test with a path.
- ;;
- *)
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_path_ac_pt_ERLC="$as_dir/$ac_word$ac_exec_ext"
- $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
- done
-IFS=$as_save_IFS
-
- ;;
-esac
-fi
-ac_pt_ERLC=$ac_cv_path_ac_pt_ERLC
-if test -n "$ac_pt_ERLC"; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_pt_ERLC" >&5
-$as_echo "$ac_pt_ERLC" >&6; }
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
- if test "x$ac_pt_ERLC" = x; then
- ERLC=""
- else
- case $cross_compiling:$ac_tool_warned in
-yes:)
-{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
-$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
-ac_tool_warned=yes ;;
-esac
- ERLC=$ac_pt_ERLC
- fi
-else
- ERLC="$ac_cv_path_ERLC"
-fi
-
-fi
-
-
-if test "$cross_compiling" = yes; then :
- { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
-$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
-as_fn_error "cannot run test program while cross compiling
-See \`config.log' for more details." "$LINENO" 5; }
-else
- cat > conftest.$ac_ext <<_ACEOF
--module(conftest).
--export([start/0]).
-
-start() ->
- halt(case erlang:system_info(wordsize) of
- 8 -> 0; 4 -> 1 end)
-.
-
-_ACEOF
-if ac_fn_erl_try_run "$LINENO"; then :
- { $as_echo "$as_me:${as_lineno-$LINENO}: found 64-bit Erlang" >&5
-$as_echo "$as_me: found 64-bit Erlang" >&6;}
- CBIT=-m64
-else
- { $as_echo "$as_me:${as_lineno-$LINENO}: found 32-bit Erlang" >&5
-$as_echo "$as_me: found 32-bit Erlang" >&6;}
- CBIT=-m32
-fi
-rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
- conftest.$ac_objext conftest.beam conftest.$ac_ext
-fi
-
- ;;
- *)
- echo "Target OS is '$target_os'"
- CBIT=""
- ;;
-esac
-CFLAGS="$CFLAGS $CBIT"
-LD_SHARED="$LD_SHARED $CBIT"
-echo "CBIT is set to '$CBIT'"
-
-cat >confcache <<\_ACEOF
-# This file is a shell script that caches the results of configure
-# tests run on this system so they can be shared between configure
-# scripts and configure runs, see configure's option --config-cache.
-# It is not useful on other systems. If it contains results you don't
-# want to keep, you may remove or edit it.
-#
-# config.status only pays attention to the cache file if you give it
-# the --recheck option to rerun configure.
-#
-# `ac_cv_env_foo' variables (set or unset) will be overridden when
-# loading this file, other *unset* `ac_cv_foo' will be assigned the
-# following values.
-
-_ACEOF
-
-# The following way of writing the cache mishandles newlines in values,
-# but we know of no workaround that is simple, portable, and efficient.
-# So, we kill variables containing newlines.
-# Ultrix sh set writes to stderr and can't be redirected directly,
-# and sets the high bit in the cache file unless we assign to the vars.
-(
- for ac_var in `(set) 2>&1 | sed -n 's/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'`; do
- eval ac_val=\$$ac_var
- case $ac_val in #(
- *${as_nl}*)
- case $ac_var in #(
- *_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5
-$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;;
- esac
- case $ac_var in #(
- _ | IFS | as_nl) ;; #(
- BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #(
- *) { eval $ac_var=; unset $ac_var;} ;;
- esac ;;
- esac
- done
-
- (set) 2>&1 |
- case $as_nl`(ac_space=' '; set) 2>&1` in #(
- *${as_nl}ac_space=\ *)
- # `set' does not quote correctly, so add quotes: double-quote
- # substitution turns \\\\ into \\, and sed turns \\ into \.
- sed -n \
- "s/'/'\\\\''/g;
- s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\\2'/p"
- ;; #(
- *)
- # `set' quotes correctly as required by POSIX, so do not add quotes.
- sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
- ;;
- esac |
- sort
-) |
- sed '
- /^ac_cv_env_/b end
- t clear
- :clear
- s/^\([^=]*\)=\(.*[{}].*\)$/test "${\1+set}" = set || &/
- t end
- s/^\([^=]*\)=\(.*\)$/\1=${\1=\2}/
- :end' >>confcache
-if diff "$cache_file" confcache >/dev/null 2>&1; then :; else
- if test -w "$cache_file"; then
- test "x$cache_file" != "x/dev/null" &&
- { $as_echo "$as_me:${as_lineno-$LINENO}: updating cache $cache_file" >&5
-$as_echo "$as_me: updating cache $cache_file" >&6;}
- cat confcache >$cache_file
- else
- { $as_echo "$as_me:${as_lineno-$LINENO}: not updating unwritable cache $cache_file" >&5
-$as_echo "$as_me: not updating unwritable cache $cache_file" >&6;}
- fi
-fi
-rm -f confcache
-
-test "x$prefix" = xNONE && prefix=$ac_default_prefix
-# Let make expand exec_prefix.
-test "x$exec_prefix" = xNONE && exec_prefix='${prefix}'
-
-# Transform confdefs.h into DEFS.
-# Protect against shell expansion while executing Makefile rules.
-# Protect against Makefile macro expansion.
-#
-# If the first sed substitution is executed (which looks for macros that
-# take arguments), then branch to the quote section. Otherwise,
-# look for a macro that doesn't take arguments.
-ac_script='
-:mline
-/\\$/{
- N
- s,\\\n,,
- b mline
-}
-t clear
-:clear
-s/^[ ]*#[ ]*define[ ][ ]*\([^ (][^ (]*([^)]*)\)[ ]*\(.*\)/-D\1=\2/g
-t quote
-s/^[ ]*#[ ]*define[ ][ ]*\([^ ][^ ]*\)[ ]*\(.*\)/-D\1=\2/g
-t quote
-b any
-:quote
-s/[ `~#$^&*(){}\\|;'\''"<>?]/\\&/g
-s/\[/\\&/g
-s/\]/\\&/g
-s/\$/$$/g
-H
-:any
-${
- g
- s/^\n//
- s/\n/ /g
- p
-}
-'
-DEFS=`sed -n "$ac_script" confdefs.h`
-
-
-ac_libobjs=
-ac_ltlibobjs=
-for ac_i in : $LIBOBJS; do test "x$ac_i" = x: && continue
- # 1. Remove the extension, and $U if already installed.
- ac_script='s/\$U\././;s/\.o$//;s/\.obj$//'
- ac_i=`$as_echo "$ac_i" | sed "$ac_script"`
- # 2. Prepend LIBOBJDIR. When used with automake>=1.10 LIBOBJDIR
- # will be set to the directory where LIBOBJS objects are built.
- as_fn_append ac_libobjs " \${LIBOBJDIR}$ac_i\$U.$ac_objext"
- as_fn_append ac_ltlibobjs " \${LIBOBJDIR}$ac_i"'$U.lo'
-done
-LIBOBJS=$ac_libobjs
-
-LTLIBOBJS=$ac_ltlibobjs
-
-
-
-: ${CONFIG_STATUS=./config.status}
-ac_write_fail=0
-ac_clean_files_save=$ac_clean_files
-ac_clean_files="$ac_clean_files $CONFIG_STATUS"
-{ $as_echo "$as_me:${as_lineno-$LINENO}: creating $CONFIG_STATUS" >&5
-$as_echo "$as_me: creating $CONFIG_STATUS" >&6;}
-as_write_fail=0
-cat >$CONFIG_STATUS <<_ASEOF || as_write_fail=1
-#! $SHELL
-# Generated by $as_me.
-# Run this file to recreate the current configuration.
-# Compiler output produced by configure, useful for debugging
-# configure, is in config.log if it exists.
-
-debug=false
-ac_cs_recheck=false
-ac_cs_silent=false
-
-SHELL=\${CONFIG_SHELL-$SHELL}
-export SHELL
-_ASEOF
-cat >>$CONFIG_STATUS <<\_ASEOF || as_write_fail=1
-## -------------------- ##
-## M4sh Initialization. ##
-## -------------------- ##
-
-# Be more Bourne compatible
-DUALCASE=1; export DUALCASE # for MKS sh
-if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then :
- emulate sh
- NULLCMD=:
- # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
- # is contrary to our usage. Disable this feature.
- alias -g '${1+"$@"}'='"$@"'
- setopt NO_GLOB_SUBST
-else
- case `(set -o) 2>/dev/null` in #(
- *posix*) :
- set -o posix ;; #(
- *) :
- ;;
-esac
-fi
-
-
-as_nl='
-'
-export as_nl
-# Printing a long string crashes Solaris 7 /usr/bin/printf.
-as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
-as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
-as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
-# Prefer a ksh shell builtin over an external printf program on Solaris,
-# but without wasting forks for bash or zsh.
-if test -z "$BASH_VERSION$ZSH_VERSION" \
- && (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
- as_echo='print -r --'
- as_echo_n='print -rn --'
-elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
- as_echo='printf %s\n'
- as_echo_n='printf %s'
-else
- if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
- as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
- as_echo_n='/usr/ucb/echo -n'
- else
- as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
- as_echo_n_body='eval
- arg=$1;
- case $arg in #(
- *"$as_nl"*)
- expr "X$arg" : "X\\(.*\\)$as_nl";
- arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
- esac;
- expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
- '
- export as_echo_n_body
- as_echo_n='sh -c $as_echo_n_body as_echo'
- fi
- export as_echo_body
- as_echo='sh -c $as_echo_body as_echo'
-fi
-
-# The user is always right.
-if test "${PATH_SEPARATOR+set}" != set; then
- PATH_SEPARATOR=:
- (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
- (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
- PATH_SEPARATOR=';'
- }
-fi
-
-
-# IFS
-# We need space, tab and new line, in precisely that order. Quoting is
-# there to prevent editors from complaining about space-tab.
-# (If _AS_PATH_WALK were called with IFS unset, it would disable word
-# splitting by setting IFS to empty value.)
-IFS=" "" $as_nl"
-
-# Find who we are. Look in the path if we contain no directory separator.
-case $0 in #((
- *[\\/]* ) as_myself=$0 ;;
- *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
- done
-IFS=$as_save_IFS
-
- ;;
-esac
-# We did not find ourselves, most probably we were run as `sh COMMAND'
-# in which case we are not to be found in the path.
-if test "x$as_myself" = x; then
- as_myself=$0
-fi
-if test ! -f "$as_myself"; then
- $as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
- exit 1
-fi
-
-# Unset variables that we do not need and which cause bugs (e.g. in
-# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1"
-# suppresses any "Segmentation fault" message there. '((' could
-# trigger a bug in pdksh 5.2.14.
-for as_var in BASH_ENV ENV MAIL MAILPATH
-do eval test x\${$as_var+set} = xset \
- && ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || :
-done
-PS1='$ '
-PS2='> '
-PS4='+ '
-
-# NLS nuisances.
-LC_ALL=C
-export LC_ALL
-LANGUAGE=C
-export LANGUAGE
-
-# CDPATH.
-(unset CDPATH) >/dev/null 2>&1 && unset CDPATH
-
-
-# as_fn_error ERROR [LINENO LOG_FD]
-# ---------------------------------
-# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are
-# provided, also output the error to LOG_FD, referencing LINENO. Then exit the
-# script with status $?, using 1 if that was 0.
-as_fn_error ()
-{
- as_status=$?; test $as_status -eq 0 && as_status=1
- if test "$3"; then
- as_lineno=${as_lineno-"$2"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
- $as_echo "$as_me:${as_lineno-$LINENO}: error: $1" >&$3
- fi
- $as_echo "$as_me: error: $1" >&2
- as_fn_exit $as_status
-} # as_fn_error
-
-
-# as_fn_set_status STATUS
-# -----------------------
-# Set $? to STATUS, without forking.
-as_fn_set_status ()
-{
- return $1
-} # as_fn_set_status
-
-# as_fn_exit STATUS
-# -----------------
-# Exit the shell with STATUS, even in a "trap 0" or "set -e" context.
-as_fn_exit ()
-{
- set +e
- as_fn_set_status $1
- exit $1
-} # as_fn_exit
-
-# as_fn_unset VAR
-# ---------------
-# Portably unset VAR.
-as_fn_unset ()
-{
- { eval $1=; unset $1;}
-}
-as_unset=as_fn_unset
-# as_fn_append VAR VALUE
-# ----------------------
-# Append the text in VALUE to the end of the definition contained in VAR. Take
-# advantage of any shell optimizations that allow amortized linear growth over
-# repeated appends, instead of the typical quadratic growth present in naive
-# implementations.
-if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then :
- eval 'as_fn_append ()
- {
- eval $1+=\$2
- }'
-else
- as_fn_append ()
- {
- eval $1=\$$1\$2
- }
-fi # as_fn_append
-
-# as_fn_arith ARG...
-# ------------------
-# Perform arithmetic evaluation on the ARGs, and store the result in the
-# global $as_val. Take advantage of shells that can avoid forks. The arguments
-# must be portable across $(()) and expr.
-if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then :
- eval 'as_fn_arith ()
- {
- as_val=$(( $* ))
- }'
-else
- as_fn_arith ()
- {
- as_val=`expr "$@" || test $? -eq 1`
- }
-fi # as_fn_arith
-
-
-if expr a : '\(a\)' >/dev/null 2>&1 &&
- test "X`expr 00001 : '.*\(...\)'`" = X001; then
- as_expr=expr
-else
- as_expr=false
-fi
-
-if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
- as_basename=basename
-else
- as_basename=false
-fi
-
-if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
- as_dirname=dirname
-else
- as_dirname=false
-fi
-
-as_me=`$as_basename -- "$0" ||
-$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
- X"$0" : 'X\(//\)$' \| \
- X"$0" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X/"$0" |
- sed '/^.*\/\([^/][^/]*\)\/*$/{
- s//\1/
- q
- }
- /^X\/\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\/\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
-
-# Avoid depending upon Character Ranges.
-as_cr_letters='abcdefghijklmnopqrstuvwxyz'
-as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
-as_cr_Letters=$as_cr_letters$as_cr_LETTERS
-as_cr_digits='0123456789'
-as_cr_alnum=$as_cr_Letters$as_cr_digits
-
-ECHO_C= ECHO_N= ECHO_T=
-case `echo -n x` in #(((((
--n*)
- case `echo 'xy\c'` in
- *c*) ECHO_T=' ';; # ECHO_T is single tab character.
- xy) ECHO_C='\c';;
- *) echo `echo ksh88 bug on AIX 6.1` > /dev/null
- ECHO_T=' ';;
- esac;;
-*)
- ECHO_N='-n';;
-esac
-
-rm -f conf$$ conf$$.exe conf$$.file
-if test -d conf$$.dir; then
- rm -f conf$$.dir/conf$$.file
-else
- rm -f conf$$.dir
- mkdir conf$$.dir 2>/dev/null
-fi
-if (echo >conf$$.file) 2>/dev/null; then
- if ln -s conf$$.file conf$$ 2>/dev/null; then
- as_ln_s='ln -s'
- # ... but there are two gotchas:
- # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
- # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
- # In both cases, we have to default to `cp -p'.
- ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
- as_ln_s='cp -p'
- elif ln conf$$.file conf$$ 2>/dev/null; then
- as_ln_s=ln
- else
- as_ln_s='cp -p'
- fi
-else
- as_ln_s='cp -p'
-fi
-rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
-rmdir conf$$.dir 2>/dev/null
-
-
-# as_fn_mkdir_p
-# -------------
-# Create "$as_dir" as a directory, including parents if necessary.
-as_fn_mkdir_p ()
-{
-
- case $as_dir in #(
- -*) as_dir=./$as_dir;;
- esac
- test -d "$as_dir" || eval $as_mkdir_p || {
- as_dirs=
- while :; do
- case $as_dir in #(
- *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
- *) as_qdir=$as_dir;;
- esac
- as_dirs="'$as_qdir' $as_dirs"
- as_dir=`$as_dirname -- "$as_dir" ||
-$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$as_dir" : 'X\(//\)[^/]' \| \
- X"$as_dir" : 'X\(//\)$' \| \
- X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$as_dir" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- test -d "$as_dir" && break
- done
- test -z "$as_dirs" || eval "mkdir $as_dirs"
- } || test -d "$as_dir" || as_fn_error "cannot create directory $as_dir"
-
-
-} # as_fn_mkdir_p
-if mkdir -p . 2>/dev/null; then
- as_mkdir_p='mkdir -p "$as_dir"'
-else
- test -d ./-p && rmdir ./-p
- as_mkdir_p=false
-fi
-
-if test -x / >/dev/null 2>&1; then
- as_test_x='test -x'
-else
- if ls -dL / >/dev/null 2>&1; then
- as_ls_L_option=L
- else
- as_ls_L_option=
- fi
- as_test_x='
- eval sh -c '\''
- if test -d "$1"; then
- test -d "$1/.";
- else
- case $1 in #(
- -*)set "./$1";;
- esac;
- case `ls -ld'$as_ls_L_option' "$1" 2>/dev/null` in #((
- ???[sx]*):;;*)false;;esac;fi
- '\'' sh
- '
-fi
-as_executable_p=$as_test_x
-
-# Sed expression to map a string onto a valid CPP name.
-as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
-
-# Sed expression to map a string onto a valid variable name.
-as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
-
-
-exec 6>&1
-## ----------------------------------- ##
-## Main body of $CONFIG_STATUS script. ##
-## ----------------------------------- ##
-_ASEOF
-test $as_write_fail = 0 && chmod +x $CONFIG_STATUS || ac_write_fail=1
-
-cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
-# Save the log message, to keep $0 and so on meaningful, and to
-# report actual input values of CONFIG_FILES etc. instead of their
-# values after options handling.
-ac_log="
-This file was extended by ejabberd $as_me 3.0.0-alpha-x, which was
-generated by GNU Autoconf 2.65. Invocation command line was
-
- CONFIG_FILES = $CONFIG_FILES
- CONFIG_HEADERS = $CONFIG_HEADERS
- CONFIG_LINKS = $CONFIG_LINKS
- CONFIG_COMMANDS = $CONFIG_COMMANDS
- $ $0 $@
-
-on `(hostname || uname -n) 2>/dev/null | sed 1q`
-"
-
-_ACEOF
-
-case $ac_config_files in *"
-"*) set x $ac_config_files; shift; ac_config_files=$*;;
-esac
-
-
-
-cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
-# Files that config.status was made for.
-config_files="$ac_config_files"
-
-_ACEOF
-
-cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
-ac_cs_usage="\
-\`$as_me' instantiates files and other configuration actions
-from templates according to the current configuration. Unless the files
-and actions are specified as TAGs, all are instantiated by default.
-
-Usage: $0 [OPTION]... [TAG]...
-
- -h, --help print this help, then exit
- -V, --version print version number and configuration settings, then exit
- --config print configuration, then exit
- -q, --quiet, --silent
- do not print progress messages
- -d, --debug don't remove temporary files
- --recheck update $as_me by reconfiguring in the same conditions
- --file=FILE[:TEMPLATE]
- instantiate the configuration file FILE
-
-Configuration files:
-$config_files
-
-Report bugs to ."
-
-_ACEOF
-cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
-ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
-ac_cs_version="\\
-ejabberd config.status 3.0.0-alpha-x
-configured by $0, generated by GNU Autoconf 2.65,
- with options \\"\$ac_cs_config\\"
-
-Copyright (C) 2009 Free Software Foundation, Inc.
-This config.status script is free software; the Free Software Foundation
-gives unlimited permission to copy, distribute and modify it."
-
-ac_pwd='$ac_pwd'
-srcdir='$srcdir'
-test -n "\$AWK" || AWK=awk
-_ACEOF
-
-cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
-# The default lists apply if the user does not specify any file.
-ac_need_defaults=:
-while test $# != 0
-do
- case $1 in
- --*=*)
- ac_option=`expr "X$1" : 'X\([^=]*\)='`
- ac_optarg=`expr "X$1" : 'X[^=]*=\(.*\)'`
- ac_shift=:
- ;;
- *)
- ac_option=$1
- ac_optarg=$2
- ac_shift=shift
- ;;
- esac
-
- case $ac_option in
- # Handling of the options.
- -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
- ac_cs_recheck=: ;;
- --version | --versio | --versi | --vers | --ver | --ve | --v | -V )
- $as_echo "$ac_cs_version"; exit ;;
- --config | --confi | --conf | --con | --co | --c )
- $as_echo "$ac_cs_config"; exit ;;
- --debug | --debu | --deb | --de | --d | -d )
- debug=: ;;
- --file | --fil | --fi | --f )
- $ac_shift
- case $ac_optarg in
- *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;
- esac
- as_fn_append CONFIG_FILES " '$ac_optarg'"
- ac_need_defaults=false;;
- --he | --h | --help | --hel | -h )
- $as_echo "$ac_cs_usage"; exit ;;
- -q | -quiet | --quiet | --quie | --qui | --qu | --q \
- | -silent | --silent | --silen | --sile | --sil | --si | --s)
- ac_cs_silent=: ;;
-
- # This is an error.
- -*) as_fn_error "unrecognized option: \`$1'
-Try \`$0 --help' for more information." ;;
-
- *) as_fn_append ac_config_targets " $1"
- ac_need_defaults=false ;;
-
- esac
- shift
-done
-
-ac_configure_extra_args=
-
-if $ac_cs_silent; then
- exec 6>/dev/null
- ac_configure_extra_args="$ac_configure_extra_args --silent"
-fi
-
-_ACEOF
-cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
-if \$ac_cs_recheck; then
- set X '$SHELL' '$0' $ac_configure_args \$ac_configure_extra_args --no-create --no-recursion
- shift
- \$as_echo "running CONFIG_SHELL=$SHELL \$*" >&6
- CONFIG_SHELL='$SHELL'
- export CONFIG_SHELL
- exec "\$@"
-fi
-
-_ACEOF
-cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
-exec 5>>config.log
-{
- echo
- sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
-## Running $as_me. ##
-_ASBOX
- $as_echo "$ac_log"
-} >&5
-
-_ACEOF
-cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
-_ACEOF
-
-cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
-
-# Handling of arguments.
-for ac_config_target in $ac_config_targets
-do
- case $ac_config_target in
- "Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;;
- "$make_mod_muc") CONFIG_FILES="$CONFIG_FILES $make_mod_muc" ;;
- "$make_mod_pubsub") CONFIG_FILES="$CONFIG_FILES $make_mod_pubsub" ;;
- "$make_mod_proxy65") CONFIG_FILES="$CONFIG_FILES $make_mod_proxy65" ;;
- "$make_eldap") CONFIG_FILES="$CONFIG_FILES $make_eldap" ;;
- "$make_pam") CONFIG_FILES="$CONFIG_FILES $make_pam" ;;
- "$make_web") CONFIG_FILES="$CONFIG_FILES $make_web" ;;
- "stun/Makefile") CONFIG_FILES="$CONFIG_FILES stun/Makefile" ;;
- "$make_tls") CONFIG_FILES="$CONFIG_FILES $make_tls" ;;
- "$make_odbc") CONFIG_FILES="$CONFIG_FILES $make_odbc" ;;
- "$make_ejabberd_zlib") CONFIG_FILES="$CONFIG_FILES $make_ejabberd_zlib" ;;
-
- *) as_fn_error "invalid argument: \`$ac_config_target'" "$LINENO" 5;;
- esac
-done
-
-
-# If the user did not use the arguments to specify the items to instantiate,
-# then the envvar interface is used. Set only those that are not.
-# We use the long form for the default assignment because of an extremely
-# bizarre bug on SunOS 4.1.3.
-if $ac_need_defaults; then
- test "${CONFIG_FILES+set}" = set || CONFIG_FILES=$config_files
-fi
-
-# Have a temporary directory for convenience. Make it in the build tree
-# simply because there is no reason against having it here, and in addition,
-# creating and moving files from /tmp can sometimes cause problems.
-# Hook for its removal unless debugging.
-# Note that there is a small window in which the directory will not be cleaned:
-# after its creation but before its name has been assigned to `$tmp'.
-$debug ||
-{
- tmp=
- trap 'exit_status=$?
- { test -z "$tmp" || test ! -d "$tmp" || rm -fr "$tmp"; } && exit $exit_status
-' 0
- trap 'as_fn_exit 1' 1 2 13 15
-}
-# Create a (secure) tmp directory for tmp files.
-
-{
- tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` &&
- test -n "$tmp" && test -d "$tmp"
-} ||
-{
- tmp=./conf$$-$RANDOM
- (umask 077 && mkdir "$tmp")
-} || as_fn_error "cannot create a temporary directory in ." "$LINENO" 5
-
-# Set up the scripts for CONFIG_FILES section.
-# No need to generate them if there are no CONFIG_FILES.
-# This happens for instance with `./config.status config.h'.
-if test -n "$CONFIG_FILES"; then
-
-
-ac_cr=`echo X | tr X '\015'`
-# On cygwin, bash can eat \r inside `` if the user requested igncr.
-# But we know of no other shell where ac_cr would be empty at this
-# point, so we can use a bashism as a fallback.
-if test "x$ac_cr" = x; then
- eval ac_cr=\$\'\\r\'
-fi
-ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' /dev/null`
-if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then
- ac_cs_awk_cr='\r'
-else
- ac_cs_awk_cr=$ac_cr
-fi
-
-echo 'BEGIN {' >"$tmp/subs1.awk" &&
-_ACEOF
-
-
-{
- echo "cat >conf$$subs.awk <<_ACEOF" &&
- echo "$ac_subst_vars" | sed 's/.*/&!$&$ac_delim/' &&
- echo "_ACEOF"
-} >conf$$subs.sh ||
- as_fn_error "could not make $CONFIG_STATUS" "$LINENO" 5
-ac_delim_num=`echo "$ac_subst_vars" | grep -c '$'`
-ac_delim='%!_!# '
-for ac_last_try in false false false false false :; do
- . ./conf$$subs.sh ||
- as_fn_error "could not make $CONFIG_STATUS" "$LINENO" 5
-
- ac_delim_n=`sed -n "s/.*$ac_delim\$/X/p" conf$$subs.awk | grep -c X`
- if test $ac_delim_n = $ac_delim_num; then
- break
- elif $ac_last_try; then
- as_fn_error "could not make $CONFIG_STATUS" "$LINENO" 5
- else
- ac_delim="$ac_delim!$ac_delim _$ac_delim!! "
- fi
-done
-rm -f conf$$subs.sh
-
-cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
-cat >>"\$tmp/subs1.awk" <<\\_ACAWK &&
-_ACEOF
-sed -n '
-h
-s/^/S["/; s/!.*/"]=/
-p
-g
-s/^[^!]*!//
-:repl
-t repl
-s/'"$ac_delim"'$//
-t delim
-:nl
-h
-s/\(.\{148\}\)..*/\1/
-t more1
-s/["\\]/\\&/g; s/^/"/; s/$/\\n"\\/
-p
-n
-b repl
-:more1
-s/["\\]/\\&/g; s/^/"/; s/$/"\\/
-p
-g
-s/.\{148\}//
-t nl
-:delim
-h
-s/\(.\{148\}\)..*/\1/
-t more2
-s/["\\]/\\&/g; s/^/"/; s/$/"/
-p
-b
-:more2
-s/["\\]/\\&/g; s/^/"/; s/$/"\\/
-p
-g
-s/.\{148\}//
-t delim
-' >$CONFIG_STATUS || ac_write_fail=1
-rm -f conf$$subs.awk
-cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
-_ACAWK
-cat >>"\$tmp/subs1.awk" <<_ACAWK &&
- for (key in S) S_is_set[key] = 1
- FS = ""
-
-}
-{
- line = $ 0
- nfields = split(line, field, "@")
- substed = 0
- len = length(field[1])
- for (i = 2; i < nfields; i++) {
- key = field[i]
- keylen = length(key)
- if (S_is_set[key]) {
- value = S[key]
- line = substr(line, 1, len) "" value "" substr(line, len + keylen + 3)
- len += length(value) + length(field[++i])
- substed = 1
- } else
- len += 1 + keylen
- }
-
- print line
-}
-
-_ACAWK
-_ACEOF
-cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
-if sed "s/$ac_cr//" < /dev/null > /dev/null 2>&1; then
- sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g"
-else
- cat
-fi < "$tmp/subs1.awk" > "$tmp/subs.awk" \
- || as_fn_error "could not setup config files machinery" "$LINENO" 5
-_ACEOF
-
-# VPATH may cause trouble with some makes, so we remove $(srcdir),
-# ${srcdir} and @srcdir@ from VPATH if srcdir is ".", strip leading and
-# trailing colons and then remove the whole line if VPATH becomes empty
-# (actually we leave an empty line to preserve line numbers).
-if test "x$srcdir" = x.; then
- ac_vpsub='/^[ ]*VPATH[ ]*=/{
-s/:*\$(srcdir):*/:/
-s/:*\${srcdir}:*/:/
-s/:*@srcdir@:*/:/
-s/^\([^=]*=[ ]*\):*/\1/
-s/:*$//
-s/^[^=]*=[ ]*$//
-}'
-fi
-
-cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
-fi # test -n "$CONFIG_FILES"
-
-
-eval set X " :F $CONFIG_FILES "
-shift
-for ac_tag
-do
- case $ac_tag in
- :[FHLC]) ac_mode=$ac_tag; continue;;
- esac
- case $ac_mode$ac_tag in
- :[FHL]*:*);;
- :L* | :C*:*) as_fn_error "invalid tag \`$ac_tag'" "$LINENO" 5;;
- :[FH]-) ac_tag=-:-;;
- :[FH]*) ac_tag=$ac_tag:$ac_tag.in;;
- esac
- ac_save_IFS=$IFS
- IFS=:
- set x $ac_tag
- IFS=$ac_save_IFS
- shift
- ac_file=$1
- shift
-
- case $ac_mode in
- :L) ac_source=$1;;
- :[FH])
- ac_file_inputs=
- for ac_f
- do
- case $ac_f in
- -) ac_f="$tmp/stdin";;
- *) # Look for the file first in the build tree, then in the source tree
- # (if the path is not absolute). The absolute path cannot be DOS-style,
- # because $ac_f cannot contain `:'.
- test -f "$ac_f" ||
- case $ac_f in
- [\\/$]*) false;;
- *) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";;
- esac ||
- as_fn_error "cannot find input file: \`$ac_f'" "$LINENO" 5;;
- esac
- case $ac_f in *\'*) ac_f=`$as_echo "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac
- as_fn_append ac_file_inputs " '$ac_f'"
- done
-
- # Let's still pretend it is `configure' which instantiates (i.e., don't
- # use $as_me), people would be surprised to read:
- # /* config.h. Generated by config.status. */
- configure_input='Generated from '`
- $as_echo "$*" | sed 's|^[^:]*/||;s|:[^:]*/|, |g'
- `' by configure.'
- if test x"$ac_file" != x-; then
- configure_input="$ac_file. $configure_input"
- { $as_echo "$as_me:${as_lineno-$LINENO}: creating $ac_file" >&5
-$as_echo "$as_me: creating $ac_file" >&6;}
- fi
- # Neutralize special characters interpreted by sed in replacement strings.
- case $configure_input in #(
- *\&* | *\|* | *\\* )
- ac_sed_conf_input=`$as_echo "$configure_input" |
- sed 's/[\\\\&|]/\\\\&/g'`;; #(
- *) ac_sed_conf_input=$configure_input;;
- esac
-
- case $ac_tag in
- *:-:* | *:-) cat >"$tmp/stdin" \
- || as_fn_error "could not create $ac_file" "$LINENO" 5 ;;
- esac
- ;;
- esac
-
- ac_dir=`$as_dirname -- "$ac_file" ||
-$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$ac_file" : 'X\(//\)[^/]' \| \
- X"$ac_file" : 'X\(//\)$' \| \
- X"$ac_file" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$ac_file" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- as_dir="$ac_dir"; as_fn_mkdir_p
- ac_builddir=.
-
-case "$ac_dir" in
-.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
-*)
- ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
- # A ".." for each directory in $ac_dir_suffix.
- ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
- case $ac_top_builddir_sub in
- "") ac_top_builddir_sub=. ac_top_build_prefix= ;;
- *) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
- esac ;;
-esac
-ac_abs_top_builddir=$ac_pwd
-ac_abs_builddir=$ac_pwd$ac_dir_suffix
-# for backward compatibility:
-ac_top_builddir=$ac_top_build_prefix
-
-case $srcdir in
- .) # We are building in place.
- ac_srcdir=.
- ac_top_srcdir=$ac_top_builddir_sub
- ac_abs_top_srcdir=$ac_pwd ;;
- [\\/]* | ?:[\\/]* ) # Absolute name.
- ac_srcdir=$srcdir$ac_dir_suffix;
- ac_top_srcdir=$srcdir
- ac_abs_top_srcdir=$srcdir ;;
- *) # Relative name.
- ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
- ac_top_srcdir=$ac_top_build_prefix$srcdir
- ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
-esac
-ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
-
-
- case $ac_mode in
- :F)
- #
- # CONFIG_FILE
- #
-
-_ACEOF
-
-cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
-# If the template does not know about datarootdir, expand it.
-# FIXME: This hack should be removed a few years after 2.60.
-ac_datarootdir_hack=; ac_datarootdir_seen=
-ac_sed_dataroot='
-/datarootdir/ {
- p
- q
-}
-/@datadir@/p
-/@docdir@/p
-/@infodir@/p
-/@localedir@/p
-/@mandir@/p'
-case `eval "sed -n \"\$ac_sed_dataroot\" $ac_file_inputs"` in
-*datarootdir*) ac_datarootdir_seen=yes;;
-*@datadir@*|*@docdir@*|*@infodir@*|*@localedir@*|*@mandir@*)
- { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&5
-$as_echo "$as_me: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&2;}
-_ACEOF
-cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
- ac_datarootdir_hack='
- s&@datadir@&$datadir&g
- s&@docdir@&$docdir&g
- s&@infodir@&$infodir&g
- s&@localedir@&$localedir&g
- s&@mandir@&$mandir&g
- s&\\\${datarootdir}&$datarootdir&g' ;;
-esac
-_ACEOF
-
-# Neutralize VPATH when `$srcdir' = `.'.
-# Shell code in configure.ac might set extrasub.
-# FIXME: do we really want to maintain this feature?
-cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
-ac_sed_extra="$ac_vpsub
-$extrasub
-_ACEOF
-cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
-:t
-/@[a-zA-Z_][a-zA-Z_0-9]*@/!b
-s|@configure_input@|$ac_sed_conf_input|;t t
-s&@top_builddir@&$ac_top_builddir_sub&;t t
-s&@top_build_prefix@&$ac_top_build_prefix&;t t
-s&@srcdir@&$ac_srcdir&;t t
-s&@abs_srcdir@&$ac_abs_srcdir&;t t
-s&@top_srcdir@&$ac_top_srcdir&;t t
-s&@abs_top_srcdir@&$ac_abs_top_srcdir&;t t
-s&@builddir@&$ac_builddir&;t t
-s&@abs_builddir@&$ac_abs_builddir&;t t
-s&@abs_top_builddir@&$ac_abs_top_builddir&;t t
-$ac_datarootdir_hack
-"
-eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$tmp/subs.awk" >$tmp/out \
- || as_fn_error "could not create $ac_file" "$LINENO" 5
-
-test -z "$ac_datarootdir_hack$ac_datarootdir_seen" &&
- { ac_out=`sed -n '/\${datarootdir}/p' "$tmp/out"`; test -n "$ac_out"; } &&
- { ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' "$tmp/out"`; test -z "$ac_out"; } &&
- { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file contains a reference to the variable \`datarootdir'
-which seems to be undefined. Please make sure it is defined." >&5
-$as_echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir'
-which seems to be undefined. Please make sure it is defined." >&2;}
-
- rm -f "$tmp/stdin"
- case $ac_file in
- -) cat "$tmp/out" && rm -f "$tmp/out";;
- *) rm -f "$ac_file" && mv "$tmp/out" "$ac_file";;
- esac \
- || as_fn_error "could not create $ac_file" "$LINENO" 5
- ;;
-
-
-
- esac
-
-done # for ac_tag
-
-
-as_fn_exit 0
-_ACEOF
-ac_clean_files=$ac_clean_files_save
-
-test $ac_write_fail = 0 ||
- as_fn_error "write failure creating $CONFIG_STATUS" "$LINENO" 5
-
-
-# configure is writing to config.log, and then calls config.status.
-# config.status does its own redirection, appending to config.log.
-# Unfortunately, on DOS this fails, as config.log is still kept open
-# by configure, so config.status won't be able to write to it; its
-# output is simply discarded. So we exec the FD to /dev/null,
-# effectively closing config.log, so it can be properly (re)opened and
-# appended to by config.status. When coming back to configure, we
-# need to make the FD available again.
-if test "$no_create" != yes; then
- ac_cs_success=:
- ac_config_status_args=
- test "$silent" = yes &&
- ac_config_status_args="$ac_config_status_args --quiet"
- exec 5>/dev/null
- $SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false
- exec 5>>config.log
- # Use ||, not &&, to avoid exiting from the if with $? = 1, which
- # would make configure fail if this is the last instruction.
- $ac_cs_success || as_fn_exit $?
-fi
-if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then
- { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: unrecognized options: $ac_unrecognized_opts" >&5
-$as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;}
-fi
-
-
-echo
-echo "********************** WARNING ! ************************"
-echo "* ejabberd master is NOT ready for real usage yet, *"
-echo "* because it is still in heavy development. *"
-echo "* Don't use ejabberd master, it is still alpha code! *"
-echo "* Please use ejabberd 2.1.x branch instead. *"
-echo "*********************************************************"
-echo