<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>2.5. OS-Specific Installation Notes</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="multiple-bz-dbs.html" title="2.4. Multiple Bugzilla databases with a single installation"><link rel="next" href="nonroot.html" title="2.6. UNIX (non-root) Installation Notes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.5. OS-Specific Installation Notes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="multiple-bz-dbs.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="nonroot.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="os-specific"></a>2.5. OS-Specific Installation Notes</h2></div></div></div><p>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.
</p><p>If you have anything to add or notes for an operating system not covered,
please file a bug in <a class="ulink" href="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla;component=Documentation" target="_top">Bugzilla Documentation</a>.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="os-win32"></a>2.5.1. Microsoft Windows</h3></div></div></div><p>
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
<a class="ulink" href="https://wiki.mozilla.org/Bugzilla:Win32Install" target="_top">
installation guide for Windows</a> is also available
if you need more help with your installation.
</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-perl"></a>2.5.1.1. Win32 Perl</h4></div></div></div><p>
Perl for Windows can be obtained from
<a class="ulink" href="http://www.activestate.com/" target="_top">ActiveState</a>.
You should be able to find a compiled binary at <a class="ulink" href="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/" target="_top">http://aspn.activestate.com/ASPN/Downloads/ActivePerl/</a>.
The following instructions assume that you are using version
5.8.1 of ActiveState.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
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.
</p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-perl-modules"></a>2.5.1.2. Perl Modules on Win32</h4></div></div></div><p>
Bugzilla on Windows requires the same perl modules found in
<a class="xref" href="installation.html#install-perlmodules" title="2.1.5. Perl Modules">Section 2.1.5, “Perl Modules”</a>. The main difference is that
windows uses <a class="glossterm" href="glossary.html#gloss-ppm"><em class="glossterm">PPM</em></a> 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:
</p><pre class="programlisting">
C:\perl> <span class="command"><strong>ppm install <module name></strong></span>
</pre><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
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 <span class="command"><strong>checksetup.pl</strong></span> as it will
tell you what package you'll need to install.
</p></td></tr></table></div><div class="tip" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="../images/tip.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
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.
</p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-http"></a>2.5.1.3. Serving the web pages</h4></div></div></div><p>
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 <a class="xref" href="security-webserver.html#security-webserver-access" title="4.2.1. Disabling Remote Access to Bugzilla Configuration Files">Section 4.2.1, “Disabling Remote Access to Bugzilla Configuration Files”</a>. More
information on configuring specific web servers can be found
in <a class="xref" href="configuration.html#http" title="2.2.4. Web server">Section 2.2.4, “Web server”</a>.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
The web server looks at <code class="filename">/usr/bin/perl</code> to
call Perl. If you are using Apache on windows, you can set the
<a class="ulink" href="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource" target="_top">ScriptInterpreterSource</a>
directive in your Apache config file to make it look at the
right place: insert the line
</p><pre class="programlisting">ScriptInterpreterSource Registry-Strict</pre><p>
into your <code class="filename">httpd.conf</code> file, and create the key
</p><pre class="programlisting">HKEY_CLASSES_ROOT\.cgi\Shell\ExecCGI\Command</pre><p>
with <code class="option">C:\Perl\bin\perl.exe -T</code> as value (adapt to your
path if needed) in the registry. When this is done, restart Apache.
</p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-email"></a>2.5.1.4. Sending Email</h4></div></div></div><p>
To enable Bugzilla to send email on Windows, the server running the
Bugzilla code must be able to connect to, or act as, an SMTP server.
</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="os-macosx"></a>2.5.2. <span class="productname">Mac OS X</span>™</h3></div></div></div><p>Making Bugzilla work on Mac OS X requires the following
adjustments.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="macosx-sendmail"></a>2.5.2.1. Sendmail</h4></div></div></div><p>In Mac OS X 10.3 and later,
<a class="ulink" href="http://www.postfix.org/" target="_top">Postfix</a>
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.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="macosx-libraries"></a>2.5.2.2. Libraries & Perl Modules on Mac OS X</h4></div></div></div><p>Apple does not include the GD library with Mac OS X. Bugzilla
needs this for bug graphs.</p><p>You can use MacPorts (<a class="ulink" href="http://www.macports.org/" target="_top">http://www.macports.org/</a>)
or Fink (<a class="ulink" href="http://sourceforge.net/projects/fink/" target="_top">http://sourceforge.net/projects/fink/</a>), both
of which are similar in nature to the CPAN installer, but install
common unix programs.</p><p>Follow the instructions for setting up MacPorts or Fink.
Once you have one installed, you'll want to use it to install the
<code class="filename">gd2</code> package.
</p><p>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 <a class="glossterm" href="glossary.html#gloss-cpan"><em class="glossterm">CPAN</em></a> to
install the GD Perl module.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>To prevent creating conflicts with the software that Apple
installs by default, Fink creates its own directory tree at
<code class="filename">/sw</code> where it installs most of
the software that it installs. This means your libraries and headers
will be at <code class="filename">/sw/lib</code> and
<code class="filename">/sw/include</code> instead of
<code class="filename">/usr/lib</code> and
<code class="filename">/usr/include</code>. When the
Perl module config script asks where your <code class="filename">libgd</code>
is, be sure to tell it
<code class="filename">/sw/lib</code>.
</p></td></tr></table></div><p>Also available via MacPorts and Fink is
<code class="filename">expat</code>. 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
command sequence:
</p><pre class="screen">
# perl -MCPAN -e'look XML::Parser'
# perl Makefile.PL EXPATLIBPATH=/sw/lib EXPATINCPATH=/sw/include
# make; make test; make install
# exit
</pre><p>
The <span class="command"><strong>look</strong></span> command will download the module and spawn
a new shell with the extracted files as the current working directory.
</p><p>
You should watch the output from these <span class="command"><strong>make</strong></span> commands,
especially <span class="quote">“<span class="quote">make test</span>”</span> as errors may prevent
XML::Parser from functioning correctly with Bugzilla.
</p><p>
The <span class="command"><strong>exit</strong></span> command will return you to your original shell.
</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="os-linux"></a>2.5.3. Linux/BSD Distributions</h3></div></div></div><p>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.
</p><p>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
<a class="ulink" href="https://wiki.mozilla.org/Bugzilla:Prerequisites" target="_top">
Bugzilla Wiki Page</a> for distro-specific installation
notes.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="multiple-bz-dbs.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="nonroot.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.4. Multiple Bugzilla databases with a single installation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.6. UNIX (non-root) Installation Notes</td></tr></table></div></body></html>
