File: INSTALL

package info (click to toggle)
bacula 9.4.4-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 22,828 kB
  • sloc: ansic: 149,796; cpp: 28,073; sh: 24,976; makefile: 4,300; perl: 3,430; sql: 1,368; python: 125; xml: 64; awk: 51; sed: 25
file content (77 lines) | stat: -rw-r--r-- 3,223 bytes parent folder | download | duplicates (10)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77

This file is rather out of date, and if you want to avoid a lot
of pain, you will read the manual, which you can find at www.bacula.org 


--------------------------------------------------------------------------
Using GNU autoconfig
--------------------------------------------------------------------------
  1.    Read the Compiling and Installing section of the HTML manual
        at http://www.bacula.org

  2.    Run   ./configure   to generate config.h and the various Makefiles.
        ./configure --help   gives a list of possible options.  Note, in
        configuring Bacula, you cannot get by with a simple ./configure,
        it is much more complicated than that (unfortunately).

        You might look at the "defaultconfig" file in the examples directory.
        It is an example of what is probably reasonable for defaults.

        Some systems require unusual options for compilation or linking that
        the `configure' script does not know about.  You can give `configure'
        initial values for variables by setting them in the environment.  Using
        a Bourne-compatible shell, you can do that on the command line like
        this:
                CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
        Or on systems that have the `env' program, you can do it like this:
                env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
        Or if you're using a non Bourne-compatible shell, you can do:
                sh -c 'CFLAGS="-O2 -g" ./configure

        A typical Bacula development configuration for Linux is:

        CFLAGS="-g -O2 -Wall" \
          ./configure \
            --sbindir=$HOME/bacula/bin \
            --sysconfdir=$HOME/bacula/bin \
            --with-pid-dir=$HOME/bacula/bin/working \
            --with-subsys-dir=$HOME/bacula/bin/working \
            --enable-smartalloc \
            --with-mysql \
            --with-working-dir=$HOME/bacula/bin/working \
            --with-dump-email=your@address.com \
            --with-job-email=your@address.com \
            --with-smtp-host=localhost


        See the README for a few additional details and the online manual
        for all the gory details:  http://www.bacula.org/rel-manual

  3.    Carefully review the output from ./configure.  If it is not
        what you want, re-run the ./configure.  Often ./configure "caches"
        things and thus remembers the last ./configure options.  If you
        want to be sure you are starting fresh after a ./configure,
        do a:

            make distclean

        before re-running ./configure.  "make distclean" wipes out any
        knowledge of the ./configure, so don't do it after you have a
        configuration that suits your needs, otherwise the "make" will
        not work.

  4.    Set any other main preferences (normally, you don't do this):
            Edit "config.h"   if you didn't use ./configure options
            If you're cross-compiling, edit the following in "config.h"

  5.    Build it (repeat step 2 as desired):
            make

  6.    Install it
            make install

  7.    Run it
            cd $HOME/bacula/bin
            ./bacula start
            ./console
            (enter commands)