|
- Timestamp:
-
May 11, 2010, 4:35:35 PM (14 years ago)
- Author:
-
jweil
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v1
|
v2
|
|
5 | 5 | * The most convenient way is to install the libbz2 packages (usually 'libbz2' and 'libbz2-devel' or similar) via your Linux distribution's package management tool (which requires root access or a friendly admin). |
6 | 6 | |
7 | | * If you don't have root access, your admin is not friendly or your OS is not Linux, you may instead get the bzip2 sources from http://www.bzip.org/ and compile it yourself. libbz2.a must be put someplace where the compiler can find it (e.g. in /usr/lib, /usr/lib64 or GiBUU/workingCode/objects/LIB/lib). |
| 7 | * If you don't have root access, your admin is not friendly or your OS is not Linux, you may instead get the bzip2 sources from http://www.bzip.org/ and compile it yourself. libbz2.a must be put someplace where the compiler can find it (e.g. in /usr/lib, /usr/lib64, /usr/local/lib, /usr/local/lib64 or GiBUU/workingCode/objects/LIB/lib). |
8 | 8 | |
9 | 9 | This should usually be sufficient for compiling GiBUU. However, in the case that you want to compile a 32-bit GiBUU binary on a 64-bit system, you may get errors like: |
… |
… |
|
21 | 21 | 4. Copy the just built libbz2.a to /usr/lib or GiBUU/workingCode/objects/LIB/lib. |
22 | 22 | |
| 23 | Two have both the 32-bit and the 64-bit version of libbz2.a installed on your system permanently, you can e.g. put one of them into /usr/lib and the other one in /usr/lib64. |
| 24 | |
| 25 | For the GiBUU developers, who work with the 'workingCode' sources via svn, it is also possible to get proper bz2 libraries via: |
| 26 | * "make buildBZIP2" (64-bit version) |
| 27 | * "make buildBZIP2_32" (32-bit version) |
| 28 | This automates the above steps, but is not available in GiBUU's open source releases, since they don't include the bz2 sources. |
|