1. Getting Started with Trilinos October 14, 2003 9:30-10:30 a.m. Jim Willenbring

2. Overview Obtaining Trilinos Tools for Users –Mailman –Bugzilla Configuring and Building Trilinos –General options –Platform and machine specific options –Troubleshooting Where to start Where to find help

3. The Trilinos Home Page http://software.sandia.gov/trilinos/ Highlights of the web page –Download page –User documentation User guide FAQ Individual package documentation

4. Instructions for obtaining Trilinos are available in the Trilinos User Guide. http://software.sandia.gov/trilinos/publications.html Two options –Download from Trilinos website. http://software.sandia.gov/trilinos/downloads.html –Check out a copy from the Trilinos CVS repository. Send a note to trilinos-help@software.sandia.gov if you have questions about obtaining Trilinos.trilinos-help@software.sandia.gov Obtaining Trilinos

5. Tools for Users Mailman –Users are encouraged to sign up for: Users lists for Trilinos and individual packages of interest. Announce lists for Trilinos and individual packages of interest. –See http://software.sandia.gov/mailman/listinfo for the complete list of mail lists.http://software.sandia.gov/mailman/listinfo –Use trilinos-help@software.sandia.gov for general help questions.trilinos-help@software.sandia.gov

6. Tools for Users (cont.) Bugzilla http://software.sandia.gov/bugzilla/ –Issue tracking tool. –Can be used to report bugs or request new features. –Please provide as much detail as possible (For example: Platform, OS, compiler versions, etc.)

7. Configuring and Building Trilinos Find an in depth discussion in the Trilinos User Guide: http://software.sandia.gov/trilinos/trilinosUserGuide.pdf General Configure options –./configure --help=recursive –Determine which Trilinos packages should be built. –Serial or MPI?

8. Configuring and Building Trilinos (cont.) Platform and machine specific options –Common options online at: http://software.sandia.gov/trilinos/configuration_manual.html –Example configure invocation scripts. Are meant to be examples only – customizations will almost always be necessary. Can be found in the Trilinos directory structure in the Trilinos/config/ directory. For example sgi64_mpi_atlantis. Users are encouraged to submit their scripts.

9. Configuring and Building Trilinos (cont.) Example invoke configure file for SGI64:../configure --enable-mpi --with-mpi-libs=-lmpi \ --enable-amesos --enable-tsfcoreutils \ --enable-amesos-umfpack \ --with-trilinos3pldir=/scratch1/jmwille/Trilinos3PL \ CFLAGS="-O2 -64" FFLAGS="-O2 -64" \ CXXFLAGS="-O2 -64 -LANG:std -LANG:ansi-for-init-scope=ON -ptused \ -DMPI_NO_CPPBIND" \ LDFLAGS=" -64 -L/usr/lib64/mips4/r10000 -L/usr/lib64/mips4 -L/usr/lib64 "

10. Configuring and Building Trilinos (cont.) Platform and machine specific options:../configure --enable-mpi --with-mpi-libs=-lmpi \ --enable-amesos --enable-amesos-slud --enable-tsfcoreutils \ --enable-amesos-umfpack \ --with-trilinos3pldir=/scratch1/jmwille/Trilinos3PL \ CFLAGS="-O2 -64" FFLAGS="-O2 -64" \ CXXFLAGS="-O2 -64 -LANG:std -LANG:ansi-for-init-scope=ON -ptused \ -DMPI_NO_CPPBIND" \ LDFLAGS=" -64 -L/usr/lib64/mips4/r10000 -L/usr/lib64/mips4 -L/usr/lib64 "

11. Configuring and Building Trilinos (cont.) Troubleshooting –The most common problems are the simple ones. Look for errors in the invoke configure file. –Autoconf is not able to detect spelling errors. –Line continuation problems --enable mpi \ –Look at the correct config.log file. (Created by Autoconf.) The config.log at the Trilinos level is not the correct config.log file. Go to the package level config.log file. For example: configure: error: /bin/sh '../../../packages/epetra/configure' failed for packages/epetra indicates that one should look at packages/epetra/config.log.

12. Troubleshooting using config.log The config.log file is very long. Follow these steps to find what you need: –Search for the string “Cache”. That should bring you a point in the file that looks like this: ## ------------------------ ## ## Cache variables. ## ## ----------------------- ## The error that caused the configure failure can be found above this point.

13. Working Through a config.log File Takes a little bit of practice. Isn’t very hard. Let’s try it. –Here is a common configure error: error: Cannot find lapack library, specify a path using --with-ldflags=-I (ex. --with-dlflags=- I/usr/path/lib) or a specific library using --with- lapack=DIR/LIB (ex. --with- lapack=/usr/path/lib/libcxml.a) We will now examine two common ways that this error can occur.

14. Where to Find Help Help link from Trilinos home page. http://software.sandia.gov/Trilinos/help.html Online FAQ section. http://software.sandia.gov/trilinos/faq.html Trilinos User Guide. http://software.sandia.gov/trilinos/publications.html Submitting a bug report. –Please provide as much detail as possible. –Attach the appropriate config.log. http://software.sandia.gov/trilinos/bug_reports.html Send an email. –trilinos-help@software.sandia.gov for general questions.trilinos-help@software.sandia.gov –trilinos-bugs@software.sandia.gov alternative to Bugzilla.trilinos-bugs@software.sandia.gov

15. Where to Find Help (cont.) Trilinos Home Page: http://software.sandia.gov/trilinos

16. Discussion Questions, comments?