Many aspects of the Bugzilla installation can be affected by the operating system you choose to install it on. Sometimes it can be made easier and others more difficult. This section will attempt to help you understand both the difficulties of running on specific operating systems and the utilities available to make it easier.
If you have anything to add or notes for an operating system not covered, please file a bug in Bugzilla Documentation.
Making Bugzilla work on Windows is more difficult than making it work on Unix. For that reason, we still recommend doing so on a Unix based system such as GNU/Linux. That said, if you do want to get Bugzilla running on Windows, you will need to make the following adjustments. A detailed step-by-step installation guide for Windows is also available if you need more help with your installation.
Perl for Windows can be obtained from ActiveState. You should be able to find a compiled binary at http://aspn.activestate.com/ASPN/Downloads/ActivePerl/. The following instructions assume that you are using version 5.8.1 of ActiveState.
These instructions are for 32-bit versions of Windows. If you are using a 64-bit version of Windows, you will need to install 32-bit Perl in order to install the 32-bit modules as described below.
Bugzilla on Windows requires the same perl modules found in Section 2.1.5, “Perl Modules”. The main difference is that windows uses PPM instead of CPAN. ActiveState provides a GUI to manage Perl modules. We highly recommend that you use it. If you prefer to use ppm from the command-line, type:
C:\perl> ppm install <module name>
The PPM repository stores modules in 'packages' that may have a slightly different name than the module. If retrieving these modules from there, you will need to pay attention to the information provided when you run checksetup.pl as it will tell you what package you'll need to install.
If you are behind a corporate firewall, you will need to let the ActiveState PPM utility know how to get through it to access the repositories by setting the HTTP_proxy system environmental variable. For more information on setting that variable, see the ActiveState documentation.
As is the case on Unix based systems, any web server should be able to handle Bugzilla; however, the Bugzilla Team still recommends Apache whenever asked. No matter what web server you choose, be sure to pay attention to the security notes in Section 4.2.1, “Disabling Remote Access to Bugzilla Configuration Files”. More information on configuring specific web servers can be found in Section 2.2.4, “Web server”.
The web server looks at
Making Bugzilla work on Mac OS X requires the following adjustments.
In Mac OS X 10.3 and later, Postfix is used as the built-in email server. Postfix provides an executable that mimics sendmail enough to fool Bugzilla, as long as Bugzilla can find it. Bugzilla is able to find the fake sendmail executable without any assistance.
Apple does not include the GD library with Mac OS X. Bugzilla needs this for bug graphs.
Follow the instructions for setting up MacPorts or Fink.
Once you have one installed, you'll want to use it to install the
Fink will prompt you for a number of dependencies, type 'y' and hit enter to install all of the dependencies and then watch it work. You will then be able to use CPAN to install the GD Perl module.
To prevent creating conflicts with the software that Apple
installs by default, Fink creates its own directory tree at
Also available via MacPorts and Fink is
expat. After installing the expat package, you
will be able to install XML::Parser using CPAN. If you use fink, there
is one caveat. Unlike recent versions of
the GD module, XML::Parser doesn't prompt for the location of the
required libraries. When using CPAN, you will need to use the following
# perl -MCPAN -e'look XML::Parser' # perl Makefile.PL EXPATLIBPATH=/sw/lib EXPATINCPATH=/sw/include # make; make test; make install # exit
The look command will download the module and spawn a new shell with the extracted files as the current working directory.
You should watch the output from these make commands, especially “make test” as errors may prevent XML::Parser from functioning correctly with Bugzilla.
The exit command will return you to your original shell.
Many Linux/BSD distributions include Bugzilla and its dependencies in their native package management systems. Installing Bugzilla with root access on any Linux/BSD system should be as simple as finding the Bugzilla package in the package management application and installing it using the normal command syntax. Several distributions also perform the proper web server configuration automatically on installation.
Please consult the documentation of your Linux/BSD distribution for instructions on how to install packages, or for specific instructions on installing Bugzilla with native package management tools. There is also a Bugzilla Wiki Page for distro-specific installation notes.