Changes between Version 11 and Version 12 of TracOnSLES9
- Timestamp:
- Mar 15, 2007, 12:53:57 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracOnSLES9
v11 v12 2 2 3 3 '''Warning: always start by reading the generic TracInstall instructions, which contains up-to-date installation instructions. In particular, the following instructions were current when Trac was at version 0.9''' 4 5 '''Update: These instructions also work with Trac 0.10.3.1, Subversion 1.3.2 and !ClearSilver 0.10.4''' 4 6 5 7 There are a number of reasons that setting up a Trac installation on SLES9 is somewhat painful. This documentation is meant to alleviate some of this pain, outlining what was an effective process for me. My particular scenario is a dual EM64T Xeon (x86_64) machine, which complicated things only slightly, in my experience. It may be possible to optimize the binaries with some -march=nocona trickery, but I haven't been so daring to date. The configure scripts may already be taking care of this. … … 40 42 As a precautionary note: I was relatively cavalier regarding installation and library paths, some being in the more traditional `/usr/local`, some finding their way to `/usr/lib64`, and so on. You may wish to specify `--prefix=[somewhere]` for all `./configure` scripts and decide where better to place things. 41 43 42 == 2.1: SQLite 3.27==44 == 2.1: SQLite (3.27 and 3.3.13 known to be ok) == 43 45 44 46 … … 53 55 }}} 54 56 55 == 2.2: pysqlite 2.0.5==57 == 2.2: pysqlite (2.0.5 and 2.3.3 known to be ok) == 56 58 (http://initd.org/pub/software/pysqlite/releases/2.0/2.0.5/ and http://initd.org/tracker/pysqlite) 57 59 … … 63 65 }}} 64 66 65 == 2.3: !ClearSilver 0.9.3 or 0.10.2==67 == 2.3: !ClearSilver == 66 68 (http://www.clearsilver.net/downloads/) 67 69 68 === 2.3.1 !ClearSilver 0.10.2 === 70 === 2.3.1 !ClearSilver 0.10.4 === 71 72 The problem with Python configuration (see 0.10.2 and the patch for it) has been solved. !ClearSilver 0.10.4 can be built like the following: 73 {{{ 74 ./configure --enable-gettext --disable-csharp --disable-ruby \ 75 --disable-perl --disable-java --disable-apache 76 make 77 make install 78 }}} 79 80 === 2.3.2 !ClearSilver 0.10.2 === 69 81 70 82 Some of the problems with 0.9.3 (below) have been fixed in this release, … … 72 84 for more information, as well as a patch that makes this work. 73 85 74 === 2.3. 2!ClearSilver 0.9.3 ===86 === 2.3.3 !ClearSilver 0.9.3 === 75 87 76 88 I used 0.9.3 because it was the lowest version that was required by Trac. I initially tried to install the newest (0.10.1), but the configure was balking at the target of x86_64-unknown-linux-gnu. There is apparently a patch that can be applied to work around this, but I did not use it. As with the other C packages, the `configure` parameters should include `--prefix=[your_location]` if you are installing somewhere outside the default. You must also pass the `--with-python=[path/bin/python]` parameter to set up the python bindings. … … 80 92 2. You may have to make a modification to the setup.py when installing the Python bindings. In my setup, the `-c` flag was passed to gcc along with `-o`, which is prohibited. I simply remove `-c` from the CFLAGS, per a newsgroups post (http://groups.yahoo.com/group/ClearSilver/message/242). 81 93 82 ==== 2.3. 2.1: Add the following line to the python/setup.py file, around line 70. ====94 ==== 2.3.3.1: Add the following line to the python/setup.py file, around line 70. ==== 83 95 84 96 {{{ … … 103 115 }}} 104 116 105 ==== 2.3. 2.2: Build and install the !ClearSilver libraries: ====117 ==== 2.3.3.2: Build and install the !ClearSilver libraries: ==== 106 118 107 119 {{{ … … 112 124 113 125 114 == 2.4: Subversion 1.2.3 == 115 (http://subversion.tigris.org/downloads/subversion-1.2.3.tar.gz) 126 == 2.4: Subversion (1.2.3 or 1.3.2; 1.4.x won't build) == 127 (http://subversion.tigris.org/downloads/subversion-1.2.3.tar.gz or http://subversion.tigris.org/downloads/subversion-1.3.2.tar.gz ; 128 Subversion 1.4 doesn't fit SLES9 well, because it needs a newer libapr0) 116 129 117 130 The build of Subversion is pretty simple once the other details are out of the way, but there are some SuSE-specific configuration things that must be cleaned up. In my case, make install broke unless I created the previously non-existent http2-prefork.conf. The install script must be determining this path somehow with APXS, but I haven't taken the time to completely understand what it's calculating, and how it diverges from the actual configuration. There are also some things that seem to fall through the cracks regarding the libraries. My procedure was: … … 132 145 }}} 133 146 134 === 2.4.3: Build and install the swig-py bindings to `/usr/local/lib` === 135 136 {{{ 137 make swig-py 138 make install-swig-py 139 }}} 140 141 === 2.4.4: Copy the python bindings to the site-packages directory, so Python can find them. (If you used a different prefix, substitute it for `/usr/local` in these steps.) === 142 143 {{{ 144 cp -R /usr/local/lib/svn-python/libsvn /usr/lib64/python2.3/site-packages 145 cp -R /usr/local/lib/svn-python/svn /usr/lib64/python2.3/site-packages 146 }}} 147 148 === 2.4.5: Copy the C library to `/usr/lib64` and update the library cache. (If you used a different prefix, substitute it for `/usr/local` in these steps.) === 147 === 2.4.3: Build and install the swig-py bindings to `/usr/lib64/python2.3/site-packages` === 148 149 You should make sure swig-py bindings get installed into this directory (by default, they are installed to $(prefix_dir)/lib), so that Python could find them. 150 {{{ 151 make swig_pydir=/usr/lib64/python2.3/site-packages \ 152 swig_pydir_extra=/usr/lib64/python2.3/site-packages \ 153 swig-py 154 make swig_pydir=/usr/lib64/python2.3/site-packages \ 155 swig_pydir_extra=/usr/lib64/python2.3/site-packages \ 156 install-swig-py 157 }}} 158 159 === 2.4.4: Copy the C library to `/usr/lib64` and update the library cache. (If you used a different prefix, substitute it for `/usr/local` in these steps.) === 149 160 {{{ 150 161 cp /usr/local/lib/libsvn_swig_py-1.so.0.0.0 /usr/lib64 … … 154 165 155 166 156 == 2.5: Trac 0.9b2==157 (http://ftp.edgewall.com/pub/trac/trac-0.9b2.tar.gz )167 == 2.5: Trac (0.9b2 or 0.10.3.1) == 168 (http://ftp.edgewall.com/pub/trac/trac-0.9b2.tar.gz or http://ftp.edgewall.com/pub/trac/trac-0.10.3.1.tar.gz) 158 169 159 170 At this point, the Trac installation should be as simple as on any other platform. I used the default installation path, `/usr/share/trac`.