mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00

BIT-1542 #merged * origin/topic/johanna/freebsd9: More detailed installation instructions for FreeBSD 9.X
231 lines
7.8 KiB
ReStructuredText
231 lines
7.8 KiB
ReStructuredText
.. _CMake: http://www.cmake.org
|
|
.. _SWIG: http://www.swig.org
|
|
.. _Xcode: https://developer.apple.com/xcode/
|
|
.. _MacPorts: http://www.macports.org
|
|
.. _Fink: http://www.finkproject.org
|
|
.. _Homebrew: http://brew.sh
|
|
.. _bro downloads page: https://www.bro.org/download/index.html
|
|
|
|
.. _installing-bro:
|
|
|
|
==============
|
|
Installing Bro
|
|
==============
|
|
|
|
.. contents::
|
|
|
|
Prerequisites
|
|
=============
|
|
|
|
Before installing Bro, you'll need to ensure that some dependencies
|
|
are in place.
|
|
|
|
Required Dependencies
|
|
---------------------
|
|
|
|
Bro requires the following libraries and tools to be installed
|
|
before you begin:
|
|
|
|
* Libpcap (http://www.tcpdump.org)
|
|
* OpenSSL libraries (http://www.openssl.org)
|
|
* BIND8 library
|
|
* Libz
|
|
* Bash (for BroControl)
|
|
* Python (for BroControl)
|
|
* C++ Actor Framework (CAF) version 0.14 (http://actor-framework.org)
|
|
|
|
To build Bro from source, the following additional dependencies are required:
|
|
|
|
* CMake 2.8 or greater (http://www.cmake.org)
|
|
* Make
|
|
* C/C++ compiler with C++11 support (GCC 4.8+ or Clang 3.3+)
|
|
* SWIG (http://www.swig.org)
|
|
* Bison (GNU Parser Generator)
|
|
* Flex (Fast Lexical Analyzer)
|
|
* Libpcap headers (http://www.tcpdump.org)
|
|
* OpenSSL headers (http://www.openssl.org)
|
|
* zlib headers
|
|
* Python
|
|
|
|
To install CAF, first download the source code of the required version from: https://github.com/actor-framework/actor-framework/releases
|
|
|
|
To install the required dependencies, you can use:
|
|
|
|
* RPM/RedHat-based Linux:
|
|
|
|
.. console::
|
|
|
|
sudo yum install cmake make gcc gcc-c++ flex bison libpcap-devel openssl-devel python-devel swig zlib-devel
|
|
|
|
* DEB/Debian-based Linux:
|
|
|
|
.. console::
|
|
|
|
sudo apt-get install cmake make gcc g++ flex bison libpcap-dev libssl-dev python-dev swig zlib1g-dev
|
|
|
|
* FreeBSD:
|
|
|
|
Most required dependencies should come with a minimal FreeBSD install
|
|
except for the following.
|
|
|
|
.. console::
|
|
|
|
sudo pkg install bash cmake swig bison python py27-sqlite3
|
|
|
|
Note that in older versions of FreeBSD, you might have to use the
|
|
"pkg_add -r" command instead of "pkg install".
|
|
|
|
For older versions of FreeBSD (especially FreeBSD 9.x), the system compiler
|
|
is not new enough to compile Bro. For these systems, you will have to install
|
|
a newer compiler using pkg; the ``clang34`` package should work.
|
|
|
|
You will also have to define several environment variables on these older
|
|
systems to use the new compiler and headers similar to this before calling
|
|
configure:
|
|
|
|
.. console::
|
|
|
|
export CC=clang34
|
|
export CXX=clang++34
|
|
export CXXFLAGS="-stdlib=libc++ -I${LOCALBASE}/include/c++/v1 -L${LOCALBASE}/lib"
|
|
export LDFLAGS="-pthread"
|
|
|
|
* Mac OS X:
|
|
|
|
Compiling source code on Macs requires first installing Xcode_ (in older
|
|
versions of Xcode, you would then need to go through its
|
|
"Preferences..." -> "Downloads" menus to install the "Command Line Tools"
|
|
component).
|
|
|
|
OS X comes with all required dependencies except for CMake_, SWIG_,
|
|
OpenSSL, and CAF. (OpenSSL used to be part of OS X versions 10.10
|
|
and older, for which it does not need to be installed manually. It
|
|
was removed in OS X 10.11). Distributions of these dependencies can
|
|
likely be obtained from your preferred Mac OS X package management
|
|
system (e.g. Homebrew_, MacPorts_, or Fink_). Specifically for
|
|
Homebrew, the ``cmake``, ``swig``, ``openssl`` and ``caf`` packages
|
|
provide the required dependencies.
|
|
|
|
|
|
Optional Dependencies
|
|
---------------------
|
|
|
|
Bro can make use of some optional libraries and tools if they are found at
|
|
build time:
|
|
|
|
* LibGeoIP (for geolocating IP addresses)
|
|
* sendmail (enables Bro and BroControl to send mail)
|
|
* curl (used by a Bro script that implements active HTTP)
|
|
* gperftools (tcmalloc is used to improve memory and CPU usage)
|
|
* jemalloc (http://www.canonware.com/jemalloc/)
|
|
* PF_RING (Linux only, see :doc:`Cluster Configuration <../configuration/index>`)
|
|
* ipsumdump (for trace-summary; http://www.cs.ucla.edu/~kohler/ipsumdump)
|
|
|
|
LibGeoIP is probably the most interesting and can be installed
|
|
on most platforms by following the instructions for :ref:`installing
|
|
libGeoIP and the GeoIP database
|
|
<geolocation>`.
|
|
|
|
|
|
Installing Bro
|
|
==============
|
|
|
|
Bro can be downloaded in either pre-built binary package or source
|
|
code forms.
|
|
|
|
|
|
Using Pre-Built Binary Release Packages
|
|
---------------------------------------
|
|
|
|
See the `bro downloads page`_ for currently supported/targeted
|
|
platforms for binary releases and for installation instructions.
|
|
|
|
* Linux Packages
|
|
|
|
Linux based binary installations are usually performed by adding
|
|
information about the Bro packages to the respective system packaging
|
|
tool. Then the usual system utilities such as ``apt``, ``dnf``, ``yum``,
|
|
or ``zypper`` are used to perform the installation.
|
|
|
|
The primary install prefix for binary packages is ``/opt/bro``.
|
|
|
|
Installing from Source
|
|
----------------------
|
|
|
|
Bro releases are bundled into source packages for convenience and are
|
|
available on the `bro downloads page`_.
|
|
|
|
Alternatively, the latest Bro development version
|
|
can be obtained through git repositories
|
|
hosted at ``git.bro.org``. See our `git development documentation
|
|
<https://www.bro.org/development/howtos/process.html>`_ for comprehensive
|
|
information on Bro's use of git revision control, but the short story
|
|
for downloading the full source code experience for Bro via git is:
|
|
|
|
.. console::
|
|
|
|
git clone --recursive git://git.bro.org/bro
|
|
|
|
.. note:: If you choose to clone the ``bro`` repository
|
|
non-recursively for a "minimal Bro experience", be aware that
|
|
compiling it depends on several of the other submodules as well.
|
|
|
|
The typical way to build and install from source is (for more options,
|
|
run ``./configure --help``):
|
|
|
|
.. console::
|
|
|
|
./configure
|
|
make
|
|
make install
|
|
|
|
If the ``configure`` script fails, then it is most likely because it either
|
|
couldn't find a required dependency or it couldn't find a sufficiently new
|
|
version of a dependency. Assuming that you already installed all required
|
|
dependencies, then you may need to use one of the ``--with-*`` options
|
|
that can be given to the ``configure`` script to help it locate a dependency.
|
|
|
|
The default installation path is ``/usr/local/bro``, which would typically
|
|
require root privileges when doing the ``make install``. A different
|
|
installation path can be chosen by specifying the ``configure`` script
|
|
``--prefix`` option. Note that ``/usr`` and ``/opt/bro`` are the
|
|
standard prefixes for binary Bro packages to be installed, so those are
|
|
typically not good choices unless you are creating such a package.
|
|
|
|
OpenBSD users, please see our `FAQ
|
|
<https://www.bro.org/documentation/faq.html>`_ if you are having
|
|
problems installing Bro.
|
|
|
|
Depending on the Bro package you downloaded, there may be auxiliary
|
|
tools and libraries available in the ``aux/`` directory. Some of them
|
|
will be automatically built and installed along with Bro. There are
|
|
``--disable-*`` options that can be given to the configure script to
|
|
turn off unwanted auxiliary projects that would otherwise be installed
|
|
automatically. Finally, use ``make install-aux`` to install some of
|
|
the other programs that are in the ``aux/bro-aux`` directory.
|
|
|
|
Finally, if you want to build the Bro documentation (not required, because
|
|
all of the documentation for the latest Bro release is available on the
|
|
Bro web site), there are instructions in ``doc/README`` in the source
|
|
distribution.
|
|
|
|
Configure the Run-Time Environment
|
|
==================================
|
|
|
|
You may want to adjust your ``PATH`` environment variable
|
|
according to the platform/shell/package you're using. For example:
|
|
|
|
Bourne-Shell Syntax:
|
|
|
|
.. console::
|
|
|
|
export PATH=/usr/local/bro/bin:$PATH
|
|
|
|
C-Shell Syntax:
|
|
|
|
.. console::
|
|
|
|
setenv PATH /usr/local/bro/bin:$PATH
|
|
|
|
Or substitute ``/opt/bro/bin`` instead if you installed from a binary package.
|
|
|