Your best bet to get Bacula compiled and running is
to read the online manual at:

  http://www.bacula.org

You will save yourself a lot of pain if you read
the manual -- it is online at the above site.
Barring reading the manual, you might try the
following:

To Configure it:

        CFLAGS="-g -O2" \
          ./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


Build Bacula:

   make

   If you are doing a port, there should be no errors.  The most
   likely source of errors will probably come in the src/stored
   directory in time.c or dev.c.  There may also be problems in
   lib/signal.c as I currently pull in all Linux signals, some of
   which may not be available on your system.

To create the database:

   src/cats/make_bacula_tables

To install:

   make install

To start it:

   cd $HOME/bacula/bin
   ./bacula start

To start it (as a developer). This is not appropriate if you
are installing Bacula.

   ./bacula start
   ./console

To stop it:

  ./bacula stop

Well, it is all just a bit more complicated than that,
but you should have the idea.

Be sure you read the chapter about testing your tape drive!
Don't waste a lot of time setting up and running Bacula, if
your drive is not supported.

FreeBSD users, pay special attention to the Device configuration
parameters needed to deal with FreeBSD tape drivers.

License:
Please see the file LICENSE for the terms of the license.

Here are a few tips from James MacLean on
making Bacula work on an AIX system -- 15 Mar 2003:

Hi Folks,

I expect that an AIX with all the latest patches and a proper gcc will
compile. It is a boring story as Kern knows :), but here are the
highlights todate.

I have had success with :

/usr/local/bin/gcc -v
Reading specs from /usr/local/lib/gcc-lib/powerpc-ibm-aix4.1.5.0/egcs-2.91.60/specs
gcc version egcs-2.91.60 19981201 (egcs-1.1.1 release)

Which was installed from www-frec.bull.com. But with that release, it
collides with sys/types.h from AIX and I had to redefine on my own in
src/bacula.h :

typedef int            crid_t;
typedef int            __daddr_t;
typedef unsigned int class_id_t;

With that I have had all parts of bacula running and did backups and a
restore fine.

So I then went to IBM's own (current) gcc :

/opt/freeware/GNUPro/bin/gcc -v
Reading specs from /opt/freeware/GNUPro/lib/gcc-lib/powerpc-ibm-aix4.3.3.0/2.9-aix51-020209/specs
gcc version 2.9-aix51-020209

from http://www-1.ibm.com/servers/aix/products/aixos/linux/download.html

And found that it was not creating libbac.a correctly. Since then I've
been trying to compile my own gcc only to find out last night after I
broke down and looked at the GCC docs that there was a known bug in the
AIX "as" compiler, for which there was a patch, and I have since applied.

So now I am trying again to compile my own gcc, so that I can then try to
compile Bacula and be comfortable that all is well with the latest Bacula
and GCC.

We are at AIX oslevel 4.3.3.0, so even though we brought it right up to
date 150 days ago, there is already 250Megs of patches for it :(. So there
may be more to this story :).

Bottom line is, yes it does work :), but because of our intstallation
here, your setup might need to be tweaked to compile it... Then again it
may not :).

How's that for a confusing Saturday story ;).

take care,
JES