Difference between revisions of "HCL cluster"
(→Compilation on HCL) |
|||
| Line 27: | Line 27: | ||
What follows is an example of installing the 'gv' (ghostview) package into a folder defined by an environment variable: <code>$APPSDIR</code> (which has a similar to purpose to <code>$ARCH</code> in the previous section). | What follows is an example of installing the 'gv' (ghostview) package into a folder defined by an environment variable: <code>$APPSDIR</code> (which has a similar to purpose to <code>$ARCH</code> in the previous section). | ||
| − | #find an RPM | + | #find an RPM file for your desired package<br/> |
#create rpm database directory in local tree (only do this once):<br/><code>mkdir -p $APPSDIR/var/lib/rpm</code> | #create rpm database directory in local tree (only do this once):<br/><code>mkdir -p $APPSDIR/var/lib/rpm</code> | ||
#initialise rpm database (do this only once also):<br/><code>rpm --initdb --root $APPSDIR</code> | #initialise rpm database (do this only once also):<br/><code>rpm --initdb --root $APPSDIR</code> | ||
| − | #check what files are installed by | + | #check what files are installed by the RPM file of your package<br/><code>rpm -qlp gv-3.6.1-4.fc4.i386.rpm</code> |
| − | #test for dependencies (install will not be successful and command will report an error accessing the root rpm database, ignore this):<br/><code>rpm -ivh gv-3.6.1-4.fc4.i386.rpm</code><br/>if a dependency is found, the RPM for it must also be found and appended to the <code>rpm -i</code> command (until no further dependencies are required. | + | #test for dependencies (install will not be successful and command will report an error accessing the root rpm database, ignore this):<br/><code>rpm -ivh gv-3.6.1-4.fc4.i386.rpm</code><br/>if a dependency is found, the RPM for it must also be found and appended to the <code>rpm -i</code> command (until no further dependencies are required). |
#do actual install to our local folder:<br/><code>rpm --root $APPSDIR --relocate /usr=$APPSDIR --nodeps -ivh gv-3.6.1-4.fc4.i386.rpm</code> | #do actual install to our local folder:<br/><code>rpm --root $APPSDIR --relocate /usr=$APPSDIR --nodeps -ivh gv-3.6.1-4.fc4.i386.rpm</code> | ||
Revision as of 17:46, 3 March 2010
Compilation on HCL
- Add to your environment
export ARCH=`uname -r`
if [ `hostname` == 'hcl13.ucd.ie' ]; then
export ARCH=`uname -r`smp
fi
- On hcl09 and hcl10, create a directory $HOME/$ARCH. Actually, 2.4.27-2-386 and 2.6.11-1.1369_FC4smp directories will be created.
- Configure all the software on hcl09 and hcl10, with
--prefix=$ARCH
Installing Precompiled Software on HCL Fedora Core 4 nodes
If you need a piece of software that is not already installed you may not need to compile it from source. It is possible to install pre-compiled packages to folders in your home directory<ref>http://www.ajay.ws/2009/7/10/install-a-rpm-in-home-directory-as-non-root</ref>, and this is often easier than compiling from source. The cluster uses two different OSes at present, Fedora Core 4 and Debian. These both have different pre-compiled package formats, RPM for Fedora and .deb for Debian. Unfortunately relocating the default install directory of a .deb package is troublesome, so this article only pertains to Fedora.
Fedora Core 4 is was EOL'd in 2006<ref>http://fedoraproject.org/wiki/LifeCycle/EOL</ref>and 4 years later there are few remaining resources supporting it. You can still find Fedora 4 RPMs at the following links (long unsearchable lists, give them time to load):
http://ftp.heanet.ie/pub/fedora-archive/fedora/linux/core/4/i386/os/Fedora/i386
http://ftp.heanet.ie/pub/fedora-archive/fedora/linux/extras/4/i386
http://ftp.heanet.ie/pub/fedora-archive/fedora/linux/core/updates/4/i386
What follows is an example of installing the 'gv' (ghostview) package into a folder defined by an environment variable: $APPSDIR (which has a similar to purpose to $ARCH in the previous section).
- find an RPM file for your desired package
- create rpm database directory in local tree (only do this once):
mkdir -p $APPSDIR/var/lib/rpm - initialise rpm database (do this only once also):
rpm --initdb --root $APPSDIR - check what files are installed by the RPM file of your package
rpm -qlp gv-3.6.1-4.fc4.i386.rpm - test for dependencies (install will not be successful and command will report an error accessing the root rpm database, ignore this):
rpm -ivh gv-3.6.1-4.fc4.i386.rpm
if a dependency is found, the RPM for it must also be found and appended to therpm -icommand (until no further dependencies are required). - do actual install to our local folder:
rpm --root $APPSDIR --relocate /usr=$APPSDIR --nodeps -ivh gv-3.6.1-4.fc4.i386.rpm
