- a supported platform;
- a working dynamic library system;
- a working lex and yacc - flex and bison should work.
Charybdis is designed with portability in mind, but does not target older systems nor those of solely academic interest.
Do note that operating systems are only supported if they are supported by their vendor.
These platforms are the best supported and should always work. They are actively tested. If you encounter problems, please file a bug.
- FreeBSD 10.x and above (i386 and amd64);
- Linux 2.6.x and above with glibc or musl (i386, x86_64 and ARM);
- Mac OS X 10.7 and above;
- Windows Vista/Server 2008 and above (x86 or x64).
These platforms are supported and occasionally tested, and most features should work, but this is not guaranteed. If you find any problems, file a bug, but as these are not regularly tested platforms, a timely resolution may not be possible.
- DragonflyBSD 4.4 and above (i386);
- Linux with uClibc (i386 or x86_64);
- NetBSD 6.1.x and above (i386, amd64);
- OpenBSD 5.6 and above (i386, amd64);
- Solaris 10 and above (i386).
Anything else that hasn't been tested. Charybdis may or may not work on it; patches welcome if they don't.
platform specific errata
These are known issues and workarounds for supported platforms:
- Mac OS X and macOS - you must set the
LIBTOOLIZEenvironment variable to point to glibtoolize before running autogen.sh:
$ brew install libtool $ LIBTOOLIZE="/opt/local/bin/glibtoolize" $ export LIBTOOLIZE $ ./autogen.sh
- FreeBSD - if you are compiling with IPv6 you may experience problems with IPv4 due to the way the socket code is written. To fix this you must
- Solaris - you may have to set your PATH to include
/usr/sbin. Solaris's default tools don't seem to play nicely with the configure script.
building from git
We no longer supply a prebuilt configure script in git, due to use of automake and libtool causing problems. You will need to run autogen.sh to build the autotools files prior to building charybdis.
feature specific requirements
- For SSL/TLS client and server connections, one of:
- OpenSSL 1.0.0 or newer (--enable-openssl);
- LibreSSL (--enable-openssl);
- mbedTLS (--enable-mbedtls);
- GnuTLS (--enable-gnutls).
- For certificate-based oper CHALLENGE - OpenSSL 1.0.0 or newer
(Using CHALLENGE is not recommended for new deployments, so if you want to use a different TLS library, feel free.)
- For ECDHE under OpenSSL, on Solaris and RHEL/Fedora (and its derivatives such as CentOS) - you will need to compile your own OpenSSL on these systems, as they have removed support for ECC/ECDHE. Alternatively, consider using another library (see above).
- to report bugs in charybdis, visit us on freenode in #charybdis
- please, read doc/index.txt to get an overview of the current documentation;
- read the NEWS.md file for what's new in this release;
- the files
/etc/resolv.confSHOULD be readable by the user running the server in order for IRCD to start with the correct settings. If these files are wrong, charybdis will try to use
127.0.0.1for a resolver as a last-ditch effort.
- the charybdis git repository can be checked-out using the following command:
git clone https://github.com/charybdis-ircd/charybdis.git
- the charybdis git repository depot can be browsed over the Internet at https://github.com/charybdis-ircd/charybdis