PLEASE KEEP THIS E-MAIL FOR FUTURE REFERENCE!!
Short version:
--------------
1. everyone needs to do a "cvs up" and "./autogen.sh" to get the new stuff
2. run "./configure"
a) to work out of your development directory, you MUST supply a --prefix
of your working directory. e.g., "configure --prefix=`pwd`"
b) if you do not supply --prefix. /opt/oscar is assumed
3. if the prefix is something other than where you ran configure, then
you must run "make install" (specifically: if you supplied
--prefix=`pwd`, then you do *NOT* have to run 'make install')
Longer version:
---------------
Ok, I *finally* got it in (85 commit e-mails; that's gotta be some
kind of record :-). This turned out to be a much larger deal than I
originally thought. Everyone will need to do a "cvs up",
"./autogen.sh" and "./configure" to get the new stuff. I also fixed a
few buglets along the way.
***HUGELY IMPORTANT NOTES***
- I fully expect there to be a few more problems to iron out with this
setup (e.g., files not listed in Makefile.am's, etc.). Please
either make the easy fixes yourself, or file bugs for the bigger
problems.
- DEVELOPERS: The procedure to run install_cluster is now like this:
shell$ cvs co oscar.sf.net:/cvsroot/oscar oscar
[...lots of output...]
shell$ cd oscar
shell$ ./autogen.sh
[...lots of output...]
shell$ ./configure --prefix="`pwd`"
[...lots of output...]
shell$ ./install_cluster <DEVICE>
Note that specifying a --prefix of the current directory is
ESSENTIAL. If you do not specify a prefix, /opt/oscar is used, and
you will be considered a "user" (vs. a "developer"), and you'll have
to follow the user directions listed below.
- USERS: The installation procedure is now like this:
shell$ tar zxf oscar-2.3.tar.gz
shell$ cd oscar-2.3
shell$ ./configure
[...output from configure...]
shell$ make install
[...output from make install...]
shell$ ./install_cluster <DEVICE>
Note that not specifying a --prefix will default to /opt/oscar. Any
prefix can actually be used (e.g., the special case for developers
where the prefix is actually the source tree).
install_cluster will look up $OSCAR_HOME before doing anything
important (if it is not already set). It will then cd to
$OSCAR_HOME directory before starting. Note that running
install_cluster from the expanded tarball (as shown above) and
$OSCAR_HOME/install_cluster are effectively equivalent.
Also note that after the user runs "make install", they can delete
the downloaded OSCAR tarball and expanded tarball; it's all been
installed to /opt/oscar.
- "make install" will install /etc/profile.d/oscar.(csh|sh) that will
set the environment variable OSCAR_HOME (note that typically only
users run "make install", not developers -- but it's still important
to note).
--> Be aware that OSCAR_HOME is now automatically set to the $prefix
for all users/shells.
--> "make uninstall" will remove these files.
Less important notes:
- "make dist" will currently only make the huge OSCAR tarball that
includes SRPMs -- the other two OSCAR tarballs do not currently get
created. I'll fix that later (I've filed a bug so that it doesn't
get forgotten).
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
