ViewVC Help
View File | Revision Log | Show Annotations | View Changeset | Root Listing
root/group/trunk/OOPSE-4/README
(Generate patch)

Comparing trunk/OOPSE-4/README (file contents):
Revision 2568 by gezelter, Mon Jan 16 23:10:15 2006 UTC vs.
Revision 2752 by gezelter, Tue May 16 02:06:37 2006 UTC

# Line 25 | Line 25 | What you need to compile and use OOPSE:
25      Architecture                CC     CXX     F90    Notes
26      -------------------------   ----   -----   -----  ----------------------
27      ix86-pc-linux-gnu           icc    icpc    ifort  (Intel versions 7-9)
28 <    powerpc-apple-darwin8.4.0   gcc    g++     xlf    (GNU v.4 / IBM XL v. 8.1)
28 >    i386-apple-darwin8.6.1      icc    icpc    ifort  (Intel version 9.1)
29 >    powerpc-apple-darwin8.6.0   gcc    g++     xlf95  (GNU v.4 / IBM XL v. 8.1)
30      x86_64-unknown-linux-gnu    pgcc   pgCC    pgf95  (Portland Group v. 6.0)
31 <    sparc-sun-solaris2.8        cc     CC      f95    (Sun ONE Studio 10)
31 >    sparc-sun-solaris2.10       cc     CC      f95    (Sun ONE Studio 10)
32      
33      We've successfully compiled OOPSE with the Pathscale c, c++, and
34      Fortran95 compilers on the  x86_64-unknown-linux-gnu architecture,
# Line 35 | Line 36 | What you need to compile and use OOPSE:
36      OOPSE to abort (rather than providing a useful error message) when
37      an error is found in the meta-data file.
38    
39 <    The GNU compilers, gcc and g++, work very well, but you will need to
40 <    use a Fortran *95* compler for the fortran side of OOPSE, and
41 <    pgf90 does not implement the required portions of the f95
42 <    language.  Fortran77 and Fortran90 (i.e. g77 and pgf90) are *not*
43 <    sufficient to compile the fortran portions of OOPSE.   Gfortran
43 <    does not yet build our fortran code, but g95 might.  If you use
44 <    one of these compilers, please let us know of any build or runtime
45 <    errors.
39 >    OOPSE uses features of the Fortran 95 language. The fortran
40 >    portions of our code will not compile if your compiler does not
41 >    support these particular features. Some (but not all) Fortran 90
42 >    compilers do support these features. None of the Fortran 77
43 >    compilers can be used to compile OOPSE.
44  
45 +    Compilers that are known to fail on OOPSE: g77, Gfortran, Older
46 +    Portland Group compilers (pgf77, pgf90).
47 +
48 +    Compilers that are known to work on OOPSE: Intel's ifort,
49 +    Pathscale's pathf95, IBM's xlf95, Portland's pgf95 (version 6 or
50 +    higher), Sun's f95. There may be others that work also.
51 +
52   2) GNU make (also known as gmake).  Regular make won't work.  
53      Really.  We've tried.  Don't bother with regular make.  
54      Seriously.  You need GNU make.  Did we mention that you

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines