Status of "Configurable" DAGH and Examples on Various Platforms

• newton.ph.utexas.edu (SGI R10000 Onyx):
  • IRIX64 newton 6.2 03131016 IP25
  • No problems
  
  
• modi4.ncsa.uiuc.edu (SGI R10000 O2000):
  • IRIX64 modi4 6.4 02121744 IP27
  • New (i.e. correct) version of AmrPar no longer builds on this machine; get:

    ld64: ERROR 33: Unresolved text symbol "_FWF" -- 1st referenced by grid.o.
    

  
  
• brahma.ticam.utexas.edu (IBM RS6000):
  • AIX brahma 2 3 000088347000
  • The previous '.__dviss' unresolved error was fixed by using the F77/F90 compiler flag

    -qarch=pwr2
    

    For the time being, execute

    setenv FFLAGS "-qarch=pwr2"
    

    before configuring on these machines. Otherwise, the Fortran flags will include

    -qextname
    

    whose use is currently incompatible with the Tutorial examples.
  • Core dump of AmrPar was due to mixture of 2D and 3D code in the ftp.cs.utexas.edu distribution.
  
  
• lonestar.cc.utexas.edu (CRAY/SGI T3E):
  • sn6507 lonestar 1.5.1.40 unicosmk CRAY T3E
  • "rnpl/wave2d" builds, but Tutorial examples won't: get

    C-167 CC: ERROR File = tportseq.C, Line = 39
      Argument of type "DOUBLE *" is incompatible with parameter of type
              "const double *".
    
        SetBaseGrid (GH,bb,shape);
                        ^
    
    CC-350 CC: ERROR File = tportseq.C, Line = 71
      More than one operator "<<" matches the specified operands.
    
                Function symbol function "ostream::operator<<(signed char)" is
                          ambiguous by inheritance.
                                  .
                                  .
                                  .
    CC-350 CC: ERROR File = tportseq.C, Line = 113
      More than one operator "<<" matches the specified operands.
    
                Function symbol function "ostream::operator<<(signed char)" is
                          ambiguous by inheritance.
                                  .
                                  .
                                  .
    

    during compile phase of tportseq.C, for example. Sources for Tutorial examples may need modification.
  
  
• charon.cc.utexas.edu (CRAY/SGI J90):
  • unicos charon 9.0.2.5 9.0.8 CRAY J90
  • DAGH builds but 'wave' example won't, get:

    CC-4 CC: ERROR File = /archive/utexas/ph/phaz337/autoconf/bbh_dagh/examples/../include/GridFunctionBndry2.h, Line = 518
      ERROR:  Not enough memory is available.
    
                         BOUNDING_BOX(gdb_pl.bndrybox(2*b,ident,DAGHNull)),
                         ^
    
    1 catastrophic error detected in the compilation of "wave.C"
    

    Get similar results (i.e. "Not enough memory is available.") compiling Tutorial examples. May be able to fix via compiler flag. SUGGESTIONS?