<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>OS-Specific Installation Notes</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="The Bugzilla Guide - 3.4.2
Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Installing Bugzilla"
HREF="installing-bugzilla.html"><LINK
REL="PREVIOUS"
TITLE="Multiple Bugzilla databases with a single installation"
HREF="multiple-bz-dbs.html"><LINK
REL="NEXT"
TITLE="UNIX (non-root) Installation Notes"
HREF="nonroot.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide - 3.4.2
Release</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="multiple-bz-dbs.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 2. Installing Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="nonroot.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="os-specific"
>2.5. OS-Specific Installation Notes</A
></H1
><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
HREF="https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
TARGET="_top"
>Bugzilla Documentation</A
>.
</P
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="os-win32"
>2.5.1. Microsoft Windows</A
></H2
><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
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"
><H3
CLASS="section"
><A
NAME="win32-perl"
>2.5.1.1. Win32 Perl</A
></H3
><P
> Perl for Windows can be obtained from
<A
HREF="http://www.activestate.com/"
TARGET="_top"
>ActiveState</A
>.
You should be able to find a compiled binary at <A
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"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><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"
><H3
CLASS="section"
><A
NAME="win32-perl-modules"
>2.5.1.2. Perl Modules on Win32</A
></H3
><P
> Bugzilla on Windows requires the same perl modules found in
<A
HREF="installation.html#install-perlmodules"
>Section 2.1.5</A
>. The main difference is that
windows uses <A
HREF="glossary.html#gloss-ppm"
><I
CLASS="glossterm"
>PPM</I
></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
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> C:\perl> <B
CLASS="command"
>ppm install <module name></B
>
</PRE
></FONT
></TD
></TR
></TABLE
><P
> The best source for the Windows PPM modules needed for Bugzilla
is probably the theory58S website, which you can add to your list
of repositories as follows (for Perl 5.8.x):
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> <B
CLASS="command"
>ppm repo add theory58S http://theoryx5.uwinnipeg.ca/ppms/</B
>
</PRE
></FONT
></TD
></TR
></TABLE
><P
> If you are using Perl 5.10.x, you cannot use the same PPM modules as Perl
5.8.x as they are incompatible. In this case, you should add the following
repository:
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> <B
CLASS="command"
>ppm repo add theory58S http://cpan.uwinnipeg.ca/PPMPackages/10xx/</B
>
</PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> In versions prior to 5.8.8 build 819 of PPM the command is
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> <B
CLASS="command"
>ppm repository add theory58S http://theoryx5.uwinnipeg.ca/ppms/</B
>
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><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 <B
CLASS="command"
>checksetup.pl</B
> as it will
tell you what package you'll need to install.
</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><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"
><H3
CLASS="section"
><A
NAME="win32-http"
>2.5.1.3. Serving the web pages</A
></H3
><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
HREF="security-webserver.html#security-webserver-access"
>Section 4.2.1</A
>. More
information on configuring specific web servers can be found
in <A
HREF="configuration.html#http"
>Section 2.2.4</A
>.
</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> The web server looks at <TT
CLASS="filename"
>/usr/bin/perl</TT
> to
call Perl. If you are using Apache on windows, you can set the
<A
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
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>ScriptInterpreterSource Registry-Strict</PRE
></FONT
></TD
></TR
></TABLE
>
into your <TT
CLASS="filename"
>httpd.conf</TT
> file, and create the key
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>HKEY_CLASSES_ROOT\.cgi\Shell\ExecCGI\Command</PRE
></FONT
></TD
></TR
></TABLE
>
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"
><H3
CLASS="section"
><A
NAME="win32-email"
>2.5.1.4. Sending Email</A
></H3
><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"
><H2
CLASS="section"
><A
NAME="os-macosx"
>2.5.2. <SPAN
CLASS="productname"
>Mac OS X</SPAN
></A
></H2
><P
>Making Bugzilla work on Mac OS X requires the following
adjustments.</P
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="macosx-sendmail"
>2.5.2.1. Sendmail</A
></H3
><P
>In Mac OS X 10.3 and later,
<A
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.</P
><P
>As of version 2.20, Bugzilla will be able to find the fake
sendmail executable without any assistance. However, you will have
to turn on the sendmailnow parameter before you do anything that would
result in email being sent. For more information, see the description
of the sendmailnow parameter in <A
HREF="parameters.html"
>Section 3.1</A
>.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="macosx-libraries"
>2.5.2.2. Libraries & Perl Modules on Mac OS X</A
></H3
><P
>Apple does not include the GD library with Mac OS X. Bugzilla
needs this for bug graphs.</P
><P
>You can use DarwinPorts (<A
HREF="http://darwinports.com/"
TARGET="_top"
>http://darwinports.com/</A
>)
or Fink (<A
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 DarwinPorts or Fink.
Once you have one installed, you'll want to use it to install the
<TT
CLASS="filename"
>gd2</TT
> 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
HREF="glossary.html#gloss-cpan"
><I
CLASS="glossterm"
>CPAN</I
></A
> to
install the GD Perl module.
</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><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
<TT
CLASS="filename"
>/sw</TT
> where it installs most of
the software that it installs. This means your libraries and headers
will be at <TT
CLASS="filename"
>/sw/lib</TT
> and
<TT
CLASS="filename"
>/sw/include</TT
> instead of
<TT
CLASS="filename"
>/usr/lib</TT
> and
<TT
CLASS="filename"
>/usr/include</TT
>. When the
Perl module config script asks where your <TT
CLASS="filename"
>libgd</TT
>
is, be sure to tell it
<TT
CLASS="filename"
>/sw/lib</TT
>.
</P
></TD
></TR
></TABLE
></DIV
><P
>Also available via DarwinPorts and Fink is
<TT
CLASS="filename"
>expat</TT
>. 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
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
> # perl -MCPAN -e'look XML::Parser' <A
NAME="macosx-look"
><IMG
SRC="../images/callouts/1.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(1)"></A
>
# perl Makefile.PL EXPATLIBPATH=/sw/lib EXPATINCPATH=/sw/include
# make; make test; make install <A
NAME="macosx-make"
><IMG
SRC="../images/callouts/2.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(2)"></A
>
# exit <A
NAME="macosx-exit"
><IMG
SRC="../images/callouts/3.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(3)"></A
>
</PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="calloutlist"
><DL
COMPACT="COMPACT"
><DT
><A
HREF="os-specific.html#macosx-look"
><IMG
SRC="../images/callouts/1.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(1)"></A
><A
HREF="os-specific.html#macosx-exit"
><IMG
SRC="../images/callouts/3.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(3)"></A
></DT
><DD
>The look command will download the module and spawn a
new shell with the extracted files as the current working directory.
The exit command will return you to your original shell.
</DD
><DT
><A
HREF="os-specific.html#macosx-make"
><IMG
SRC="../images/callouts/2.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(2)"></A
></DT
><DD
>You should watch the output from these make commands,
especially <SPAN
CLASS="QUOTE"
>"make test"</SPAN
> as errors may prevent
XML::Parser from functioning correctly with Bugzilla.
</DD
></DL
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="os-linux"
>2.5.3. Linux Distributions</A
></H2
><P
>Many Linux distributions include Bugzilla and its
dependencies in their native package management systems.
Installing Bugzilla with root access on any Linux 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
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
HREF="http://wiki.mozilla.org/Bugzilla:Linux_Distro_Installation"
TARGET="_top"
> Bugzilla Wiki Page</A
> for distro-specific installation
notes.
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="multiple-bz-dbs.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="nonroot.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Multiple Bugzilla databases with a single installation</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installing-bugzilla.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>UNIX (non-root) Installation Notes</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
distrib
>
Mandriva
>
2010.0
>
i586
>
media
>
contrib-release
>
by-pkgid
>
eede4b249967833a1b10737cc411ef80
>
files
>
729
