| 1 |
-= libGringotts installation instructions =- |
| 2 |
|
| 3 |
Hi! |
| 4 |
you may have downloaded libgringotts mainly in three forms: the |
| 5 |
CVS repository image, the tarball or an RPM file. Here is how to handle |
| 6 |
each of them: |
| 7 |
|
| 8 |
-= CVS=- |
| 9 |
|
| 10 |
You can access to cvs repository of Pluto-devel with these data: |
| 11 |
|
| 12 |
CVSROOT: :pserver:[email protected]:/Devel |
| 13 |
password: anonymous |
| 14 |
|
| 15 |
the directory to checkout is called "gringotts". If you download |
| 16 |
libGringotts from CVS, it will miss all the various files generated |
| 17 |
by the GNU build tools. So, you need to re-create them. In order |
| 18 |
to do this, you'll need: |
| 19 |
|
| 20 |
Autoconf >= 2.52 |
| 21 |
Automake = 1.4 |
| 22 |
|
| 23 |
now, cd to the libgringotts dir and type: |
| 24 |
|
| 25 |
sh autogen.sh |
| 26 |
./configure |
| 27 |
make dist |
| 28 |
|
| 29 |
after these steps, you should have in your current directory a file |
| 30 |
called libgringotts-x.y.z.tar.gz. Please read the next section to |
| 31 |
learn how to handle it. |
| 32 |
|
| 33 |
-= Tarball =- |
| 34 |
|
| 35 |
So, you have a tar file, hm? These instructions will deal with a |
| 36 |
|
| 37 |
libgringotts-x.y.z.tar.gz |
| 38 |
|
| 39 |
file; if you've a .tar.bz2 one, you should know how to adapt them to |
| 40 |
it. If not, just do a |
| 41 |
|
| 42 |
bunzip2 libgringotts-x.y.z.tar.bz2 |
| 43 |
gzip --best libgringotts-x.y.z.tar |
| 44 |
|
| 45 |
to convert it. Well, please unarchive it and go to its dir: |
| 46 |
|
| 47 |
tar xzf libgringotts-x.y.z.tar.gz |
| 48 |
cd libgringotts-x.y.z |
| 49 |
|
| 50 |
in order to compile it, you will need: |
| 51 |
|
| 52 |
libmcrypt (>= 2.4.21) |
| 53 |
http://mcrypt.hellug.gr |
| 54 |
|
| 55 |
mhash (>= 0.8.13) |
| 56 |
http://mhash.sf.net |
| 57 |
|
| 58 |
the specified package versions are simply those I use; if you have |
| 59 |
older versions, libGringotts may or may not compile. Once checked this, |
| 60 |
do a simple |
| 61 |
|
| 62 |
./configure |
| 63 |
make |
| 64 |
make check |
| 65 |
make install |
| 66 |
|
| 67 |
sequence to build, check and install it. |
| 68 |
|
| 69 |
To build an RPM package from the tarball, simply do: |
| 70 |
|
| 71 |
rpm -tb --clean libgringotts-x.y.z.tar.bz2 |
| 72 |
|
| 73 |
or, in a rpm 4.1-based system such as RedHat 8.0, |
| 74 |
|
| 75 |
rpmbuild -tb --clean libgringotts-x.y.z.tar.bz2 |
| 76 |
|
| 77 |
to build a binary package; notice that you'll need the bz2 tarball |
| 78 |
(simply recompress it if you have a gz one). "-ts" will build a |
| 79 |
source RPM. After this, read on. |
| 80 |
|
| 81 |
-= RPM =- |
| 82 |
|
| 83 |
Finally, let's suppose you have an RPM. libGringotts behave just normally, |
| 84 |
so to compile a source RPM you'll do: |
| 85 |
|
| 86 |
rpm --rebuild libgringotts-x.y.z-1.src.rpm |
| 87 |
|
| 88 |
or, in a rpm 4.1-based system such as RedHat 8.0, |
| 89 |
|
| 90 |
rpmbuild --rebuild libgringotts-x.y.z-1.src.rpm |
| 91 |
|
| 92 |
To specify some configure flags for the compilation process, set the |
| 93 |
variable $GRG_COMPILE_FLAGS: |
| 94 |
|
| 95 |
GRG_COMPILE_FLAGS="--with-gnu-ld" rpm --rebuild [...] |
| 96 |
|
| 97 |
To install the binary ones, you can do: |
| 98 |
|
| 99 |
rpm -Uvh libgringotts-x.y.z-1.i386.rpm |
| 100 |
rpm -Uvh libgringotts-devel-x.y.z-1.i386.rpm |
| 101 |
|
| 102 |
easy, ain't it? Here we are, have fun! |
| 103 |
|
| 104 |
-- Mano :) |