On Thu, 6 May 2004, John Matrow wrote:
> I copied it to a compute node and got:
> rpm -i /usr/src/redhat/RPMS/i386/lam-7.0.5-1.i386.rpm [apollo]
> error: Failed dependencies:
> gcc is needed by lam-7.0.5-1
> gcc-c++ is needed by lam-7.0.5-1
> gcc-g77 is needed by lam-7.0.5-1
The RPM contains mpicc & co. compiler wrappers which need the
underlying compiler to do their job. So installing the RPM requires
the gcc suite to be installed.
Suggestion for LAM developers: would it make sense to split the LAM
RPM into 'lam' and 'lam-devel' where 'lam-devel' would contain the
things required to compile/link MPI programs, while 'lam' will contain
only the runtime stuff. This is commonly done for many RPM packages.
> Not knowing anything about GCC, I copied gcc and g77 to /usr/bin on
> the node but it didn't help.
Copying files around is not a sensible approach on a RPM-based system.
One of the main features of the RPM packaging system is that it tracks
files that were installed in the system, such that it can also delete
them. If you just put files in the system without RPM knowing about
them, you'll soon loose track about these files and you'll start
wondering what they are doing and what will break if you remove them.
The RPM file database is updated when a RPM package is installed, so
you should add gcc/g++/g77 RPM packages to your systems - and they'll
actually contain much more than the /usr/bin executables. You should
be able to find these RPMs on the CDs or in the networked directory
that you used to install the nodes.
--
Bogdan Costescu
IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
E-mail: Bogdan.Costescu_at_[hidden]
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
