User`s guide

IST-033576 D2.1.4
% r p m b u i l d −−r e b u i l d b l c r −X. Y. Z−N. s r c . rpm −−t a r g e t
ARCH
replacing blcr-X.Y.Z-N.src.rpm with the correct filename, and ARCH with a
specific target CPU. If you don’t know your target, try uname -p to determine it.
If you don’t specify a –target, the default will depend on the version of rpmbuild
and may be i386 (which will be rejected). See the documentation for rpmbuild for
more information on building binary RPMs from source RPMs.
The RPMs should build without error. However, if not building for the running
kernel, you may see a warning about this. You will see the location of the binary
RPMs in the last few lines of output from rpmbuild - something like this:
/ u s r / s r c / r e d h a t / RPMS / i68 6 / b l c r −0.6.1 −1. i 6 8 6 . rpm
/ u s r / s r c / r e d h a t / RPMS / i68 6 / b l c r −l i b s −0.6.1 −1. i 6 8 6 . rpm
/ u s r / s r c / r e d h a t / RPMS / i68 6 / b l c r −de v e l −0.6.1 −1. i 6 8 6 . rpm
/ u s r / s r c / r e d h a t / RPMS / i68 6 / b l c r −mo dules \ _2 . 6 . 1 2 \ _1
.2 34 −0 .6 .1 −1 . i 6 8 6 . rpm
/ u s r / s r c / r e d h a t / RPMS / i68 6 / b l c r −t e s t s u i t e −0.6. 1 −1. i 6 8 6 .
rpm
You should note that the kernel version 2.6.12-1.234 has become 2.6.12_1.234
in the name of the blcr-modules package (a change of a hyphen to an underscore).
In most cases, you will want to install the blcr, blcr-libs and blcr-modules
binary RPMS. The blcr-devel is only required on machines on which you will
compiling/linking source code against BLCR’s libraries. So, for a cluster you
may want to install blcr-devel only on the front-end node(s).
The blcr-testsuite RPM is optional. You may install and run the testsuite
(/usr/libexec/blcr-testsuite/RUN_ME) if you wish to verify correct operation of
BLCR. You may be asked to do this if you report bugs to us.
A.4 For more information
For more information on Berkeley Lab Checkpoint/Restart for Linux, visit the
project home page: http://ftg.lbl.gov/checkpoint To report bugs (or look for bug
fixes prior to reporting new ones), visit http://mantis.lbl.gov/bugzilla
XtreemOS–Integrated Project 38/49