The "generic" notes for putting this thing together are below.  Here's theshort version.1.) *** Make sure you have libpcap installed!!! ***2.) ./configure3.) make4.) make install5.) Create a sample rules file (if you want to use rules, check out the     included snort.conf file)6.) snort -?7.) If you've used previous versions of Snort, you may need to rewrite your    rules to make them compliant to the rules format.  See     snort_manual.pdf or http://www.snort.org for more information. 8.) Have fun!Any questions?  Sign up to the snort-users mailing list at http://www.snort.org!Snort Configure-time switches=============================`--enable-debug'     Enable debugging options (bugreports and developers only).     `--enable-pthread'     Enable pthread support (causes snort to be linked with libpthread).`--enable-prelude'     Enable Prelude Hydrid IDS support.`--enable-rulestate'     Enable rule state configuration feature that seperates the rule     state (enabled/disabled) from the action (alert, drop, log, etc)     and definition.`--enable-dynamicplugin'     Enable dynamically loadable preprocessors, detection engine     and rules libraries.`--enable-timestats'     Enable real-time performance statistics.`--enable-perfprofiling'     Enable performance profiling of individual rules and preprocessors.`--enable-linux-smp-stats'     Enable CPU performance statistics through proc.`--enable-inline'     Use the libipq interface for inline mode.  May require --with-libipq     options.`--enable-ipfw'     Use the IPFW divert sockets for inline mode.`--enable-react'     Enable interception and termination of offending HTTP accesses.`--enable-flexresp'     Enable the 'Flexible Response' code, that allows you to     cancel hostile connections on IP-level when a rule matches.     When you enable this feature, you also need the 'libnet'-library     that can be found at http://www.packetfactory.net/libnet.      See README.FLEXRESP for details.`--enable-flexresp2'     Enable the 'Flexible Response, version 2' code, that allows you to     cancel hostile connections on IP-level when a rule matches.     When you enable this feature, you also need the 'libnet'-library     that can be found at http://www.packetfactory.net/libnet.      See README.FLEXRESP2 for details.`--enable-aruba'     Enable the Aruba output plugin capability that allows you to     send information to an Aruba Networks Mobility Controller.  See     README.ARUBA for details.`--enable-gre'     Enable GRE decoder. Allows Snort to decode GRE encapsulated traffic.     Only supports GRE over IP.  Only one layer of encapsulation will be     decoded - packets with multiple GRE headers will be alerted and     discarded/blocked.`--with-snmp'     Enable SNMP alerting code.`--with-mysql=DIR'    Support for mysql, turn this on if you want to use ACID with MySQL.    NOTE: Specifying a directory will be deprecated in the future.    `--with-mysql-libraries=DIR'    Specify location for mysql client library.    `--with-mysql-includes=DIR'    Specify location for mysql header files.    `--with-odbc=DIR'    Support for ODBC databases, turn this on if you want to use ACID with a    non-listed DB.    `--with-postgresql=DIR'    Support for Postgresql databases, turn this on if you want to use ACID with    PostgreSQL.    `--with-oracle=DIR'    Support for Oracle databases, turn this on if you want to use ACID with     Oracle.    `--with-openssl=DIR'    Support for openssl (used by the XML output plugin).`--with-libpq-includes=DIR'     Set the include directories for Postgres SQL database support to DIR.`--with-libpq-libraries=DIR'     Set the library directories for Postgres SQL database support to DIR.       Setting both of these values enables the Postgres output plugin module.`--with-libpcap-includes=DIR'     If the configuration script can't find the libpcap include files on its      own, the path can be set manually with this switch.`--with-libpcap-libraries=DIR'     If the configuration script can't find the libpcap library files on its      own, the path can be set manually with this switch.`--with-libxml2-includes=DIR'      Libxml2 include directory.`--with-libxml2-libraries=DIR'      Libxml2 library directory.    `--with-libntp-libraries=DIR'     Libntp library directory.    `--with-libidmef-includes=DIR'      Libidmef include directory.    `--with-libidmef-libraries=DIR'      Libidmef library directory.Basic Installation==================   These are generic installation instructions.   The `configure' shell script attempts to guess correct values forvarious system-dependent variables used during compilation.  It usesthose values to create a `Makefile' in each directory of the package.It may also create one or more `.h' files containing system-dependentdefinitions.  Finally, it creates a shell script `config.status' thatyou can run in the future to recreate the current configuration, a file`config.cache' that saves the results of its tests to speed upreconfiguring, and a file `config.log' containing compiler output(useful mainly for debugging `configure').   If you need to do unusual things to compile the package, please tryto figure out how `configure' could check whether to do them, and maildiffs or instructions to the address given in the `README' so they canbe considered for the next release.  If at some point `config.cache'contains results you don't want to keep, you may remove or edit it.   The file `configure.in' is used to create `configure' by a programcalled `autoconf'.  You only need `configure.in' if you want to changeit or regenerate `configure' using a newer version of `autoconf'.The simplest way to compile this package is:  1. `cd' to the directory containing the package's source code and type     `./configure' to configure the package for your system.  If you're     using `csh' on an old version of System V, you might need to type     `sh ./configure' instead to prevent `csh' from trying to execute     `configure' itself.     Running `configure' takes awhile.  While running, it prints some     messages telling which features it is checking for.  2. Type `make' to compile the package.  3. Optionally, type `make check' to run any self-tests that come with     the package.  4. Type `make install' to install the programs and any data files and     documentation.  5. You can remove the program binaries and object files from the     source code directory by typing `make clean'.  To also remove the     files that `configure' created (so you can compile the package for     a different kind of computer), type `make distclean'.  There is     also a `make maintainer-clean' target, but that is intended mainly     for the package's developers.  If you use it, you may have to get     all sorts of other programs in order to regenerate files that came     with the distribution.Compilers and Options=====================   Some systems require unusual options for compilation or linking thatthe `configure' script does not know about.  You can give `configure'initial values for variables by setting them in the environment.  Usinga Bourne-compatible shell, you can do that on the command line likethis:     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configureOr on systems that have the `env' program, you can do it like this:     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configureCompiling For Multiple Architectures====================================   You can compile the package for more than one kind of computer at thesame time, by placing the object files for each architecture in theirown directory.  To do this, you must use a version of `make' thatsupports the `VPATH' variable, such as GNU `make'.  `cd' to thedirectory where you want the object files and executables to go and runthe `configure' script.  `configure' automatically checks for thesource code in the directory that `configure' is in and in `..'.   If you have to use a `make' that does not supports the `VPATH'variable, you have to compile the package for one architecture at a timein the source code directory.  After you have installed the package forone architecture, use `make distclean' before reconfiguring for anotherarchitecture.Installation Names==================   By default, `make install' will install the package's files in`/usr/local/bin', `/usr/local/man', etc.  You can specify aninstallation prefix other than `/usr/local' by giving `configure' theoption `--prefix=PATH'.   You can specify separate installation prefixes forarchitecture-specific files and architecture-independent files.  If yougive `configure' the option `--exec-prefix=PATH', the package will usePATH as the prefix for installing programs and libraries.Documentation and other data files will still use the regular prefix.   In addition, if you use an unusual directory layout you can giveoptions like `--bindir=PATH' to specify different values for particularkinds of files.  Run `configure --help' for a list of the directoriesyou can set and what kinds of files go in them.   If the package supports it, you can cause programs to be installedwith an extra prefix or suffix on their names by giving `configure' theoption `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.