[or-cvs] [tor/maint-0.2.1] updated rpm instructions for realtime libevent.
nickm at seul.org
Fri Jul 3 01:42:18 UTC 2009
Author: Andrew Lewman <andrew at torproject.org>
Date: Thu, 2 Jul 2009 17:57:47 -0400
Subject: updated rpm instructions for realtime libevent.
doc/tor-rpm-creation.txt | 67 +++++++++++-----------------------------------
1 files changed, 16 insertions(+), 51 deletions(-)
diff --git a/doc/tor-rpm-creation.txt b/doc/tor-rpm-creation.txt
index a8280fe..3fc6bde 100644
@@ -2,60 +2,25 @@
The process used to create the official rpms is as follows:
-Download and Extract the latest tor source code from https://www.torproject.org/.
-In the resulting directory:
-You should have at least two, maybe three, rpms. There should be the binary
-i386.rpm, a src.rpm, and on redhat/centos machines, a debuginfo.rpm.
-## Optional customization
-If you wish to further tune Tor binaries in rpm format beyond this list,
-see the GCC doc page for further options:
-The tor.spec.in file contains the basic info needed to tune the binaries
-produced in rpm format. The key parameters to tune are located in the
-third section of the tor.spec.in file. Locate the section similar to
+Download latest stable libevent from
-## Target a specific arch and OS
-# default is i386 linux
-%define target gnu
-%define target_cpu i386
-%define target_os linux
+The first step of compiling libevent is to configure it as follows:
+./configure --enable-static --disable-shared
-The three parameters: target, target_cpu, and target_os are used
-throughout the "make dist-rpm" process. They control the parameters
-passed to "configure" and the final tuning of the binaries produced.
-The default settings, as shown above, create binaries for the widest
-range of Intel x86 or x86-compatible architectures.
+Complete the "make" and "make install". You will need to be root,
+or sudo -s, to complete the "make install".
-The parameters can be set as follows:
-The "target" parameter:
-This should be "gnu", "redhat", or the short name of your linux distribution.
-Other possibilities are "mandrake" or "suse". This is passed to
-"configure" through the --host, --build, and --target parameters.
-Therefore, this "target" parameter must be a valid OS for "configure" as
-The "target_cpu" parameter:
-This parameter controls the optimization and tuning of your binaries via
-gcc and "configure". This parameter is passed to gcc via the -mtune= or
--mcpu= options. The "configure" script will also receive this parameter
-through the --host, --build, and --target parameters. Therefore, this
-"target_cpu" parameter must be valid for both gcc and "configure". A
-few common options for this parameter may be "athlon64, i686, pentium4" or
-The "target_os" parameter:
-This parameter controls the target operating system. Normally, this is
-only "linux". If you wish to build rpms for a non-linux operating
-system, you can replace "linux" with your operating system.
+Check for a successful universal binary of libevent.a in, by default,
+/usr/local/lib by using the following command:
+ "file /usr/local/lib/libevent.a"
+Download and Extract the latest tor source code from
+In the resulting directory:
+You should have at least two, maybe three, rpms. There should be the binary
+i386.rpm, a src.rpm, and on redhat/centos machines, a debuginfo.rpm.
More information about the tor-commits