Steve Correll post:
The first set of errors (the ones with "std::" in them) suggest that
the compiler or the object file hello++.o generated by it are failing
to link with C++ runtime libraries. Do you need to set a CXX
environment variable analogous to the CC, FC, and F90 variables? Did
you mean to specify "-c++=pathCC" (the Pathscale C++ compiler name
ends in uppercase "CC") rather than "-c++=pathcc" (the C compiler uses
lowercase "cc")?
The Pathscale compiler can generate object files to interoperate with
versions 3, 4.0, or 4.2 of the GNU compiler (those versions are
mutually incompatible, unfortunately.) Normally it defaults to the
installed version of GNU, though it also provides command line
switches -gnu3, -gnu40, and -gnu42 (this feature does require that the
corresponding versions of GNU header files and libraries are
installed, whereas Linux distributions usually provide only one
version.) If my suggestions in the previous paragraph aren't helpful,
there could be an installation problem with Pathscale or GNU, or the
object file hello++.o might be a leftover created by or for a no-
longer-installed version of GNU. If your support contract is in force,
the folks at
supp...@pathscale.com would be happy to help: start by
sending them the output of the pathbug-helper program along with your
description of the symptoms.
The second set of errors suggests that the variable FILENM needs to be
declared inside procedures SETUP_BTIO and ACCUMULATE_NORMS using a
statement (such as INTEGER, REAL, or LOGICAL) that would give it an
explicit type. If the variable is already being declared in such a
statement, the problem is deeper, but again the folks at
supp...@pathscale.com can help.
Steve Correll (employed by, not officially speaking for, Pathscale--
and not a C++ expert)