I think the RPMs you just built is conflicting with the LAM package that is currently installed with Oscar. I don't have any solutions to offer, but I would suggest you try to install/upgrade the RPM on one nodes to test first.
I suspect it would work if you erase the original LAM RPM and then install the new one, but it might break the the MPI setup for Oscar...
Cheers,
Bernard
Mark Leverentz wrote:
Okay, so I got it to build the RPMS, and I got them installed on the head node. How do I get them installed on the client nodes (and do I even need to install them on the client nodes)? I though I could do something like this:
chroot /var/lib/systemimager/... /bin/bash rpm -Uvh lam-* cpushimage ...
but rpm is giving me these failed dependancies on the client image:
error: failed dependencies: lam-oscar is needed by lam-with-gm-oscar-module-7.0-2 lam-oscar is needed by lam-with-gm-oscar-7.0-2
I assume the problem has to do with the fact that my previous lam installation was just built from source and installed in the /home/ tree on the head node where all the slaves could see it. It seems strange that these packages would depend on what would appear to be themselves...Do you know what the problem is here?
On Wednesday September 24 2003 10:09 am, Jeff Squyres wrote:
On Wed, 24 Sep 2003, Mark Leverentz wrote:
I believe the proper way to handle this is to use switcher. Looking at switcher's man page will give you a good idea about the OSCAR philosphy on this. Also, searching through the archives of this mailing list may be helpful to you, as using the intel compiler with MPICH or LAM is something that has been addressed before.
As the switcher author, I just sent a reply about this as well.
Modules are your friends! :-)
On a related note, are there any plans to build an official RPM of LAM or MPICH that uses the intel compiler? I understand the recommended way to do this currently is to use a source RPM with a modified spec file, but I'm really not sure how this process works...could anyone enlighten me?
The possibility exists. Right now it's more of a support issue for us -- we don't have the cycles to make/support all these different RPM's. :-\ But the SRPM is there, and it should be relatively straightforward to build with your own, custom compilers.
You should be able to do the following (assuming sh-flavored shell):
# export CC=icc # export CXX=icc # export FC=if77 # rpmbuild --rebuild /path/to/srpm/file
The key here is setting the CC, CXX, and FC environment variables before running the rpmbuild command. This will tell LAM's configure script to use those compilers instead of the defaults (typically gcc, g++, g77).
(you can also do this as a normal user if you setup some additional directories and $HOME/.rpmmacros file -- ping me if you want to know the details of this)
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
