Changes between Version 8 and Version 9 of TracOnSLES9
- Timestamp:
- Feb 16, 2006, 7:35:25 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracOnSLES9
v8 v9 59 59 }}} 60 60 61 == 2.3: !ClearSilver 0.9.3 ==61 == 2.3: !ClearSilver 0.9.3 or 0.10.2 == 62 62 (http://www.clearsilver.net/downloads/) 63 64 === 2.3.1 !ClearSilver 0.10.2 === 65 66 Some of the problems with 0.9.3 (below) have been fixed in this release, 67 but a couple have not been fixed. Please see [wiki:TracOnSLES9ClearSilverFix] 68 for more information, as well as a patch that makes this work. 69 70 === 2.3.2 !ClearSilver 0.9.3 === 63 71 64 72 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. … … 68 76 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). 69 77 70 === 2.3.1: Add the following line to the python/setup.py file, around line 70.===78 ==== 2.3.2.1: Add the following line to the python/setup.py file, around line 70. ==== 71 79 72 80 {{{ … … 91 99 }}} 92 100 93 === 2.3.2: Build and install the !ClearSilver libraries:===101 ==== 2.3.2.2: Build and install the !ClearSilver libraries: ==== 94 102 95 103 {{{