Re: a problem about NPB MPI benchmark , pathscale：pathf90
- From: freshman <eirc.lew@xxxxxxxxx>
- Date: Wed, 15 Oct 2008 02:35:00 -0700 (PDT)
On Oct 15, 2:09 am, Steven Correll <steven.corr...@xxxxxxxxx> wrote:
On Oct 14, 2:36 am, kinglu <xingjin...@xxxxxxxxx> wrote:
Hi all
Recently, I compile the benchmark of NPB3.3-MPI, and my platform is
AMD opteron 2350 Quad cpu. When I install my mpich like belows:
1)export CC=pathcc
export FC=pathf90
export F90=pathf90
export RSHCOMMAND=ssh
2)
../mpich-1.2.7p1/configure --prefix=/home/lxj/mpich -c++=pathcc -opt=-
O3 --with-device=ch_p4 --enable-f90 --enable-f90modules --with-romio --
disable-weak-symbols
3) make
4) make install
At 4) there were errors as belows:
home/lxj/mpich/bin/mpicxx -o hello++ hello++.o
hello++.o(.text+0x10): In function `global destructors keyed to main':
: undefined reference to `std::ios_base::Init::~Init()'
hello++.o(.text+0x99): In function `main':
: undefined reference to `std::basic_ostream<char,
std::char_traits<char> >& std::operator<< <std::char_traits<char>
(std::basic_ostream<char, std::char_traits<char> >&, char const*)'
Can you help me about the problem ? and when I compile BT of NPB-MPI,
there were errors too. Such as:
write (newfilenm, 996) filenm,node
^
pathf95-113 pathf90: ERROR SETUP_BTIO, File = epio.f, Line = 17,
Column = 34
IMPLICIT NONE is specified in the local scope, therefore an explicit
type must be specified for data object "FILENM".
write (newfilenm, 996) filenm,node
^
pathf95-113 pathf90: ERROR ACCUMULATE_NORMS, File = epio.f, Line =
138, Column = 34
IMPLICIT NONE is specified in the local scope, therefore an explicit
type must be specified for data object "FILENM".
I have been in trouble for days, wish you can help me.
Thank you.
Eric
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...@xxxxxxxxxxxxx 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...@xxxxxxxxxxxxx can help.
Steve Correll (employed by, not officially speaking for, Pathscale--
and not a C++ expert)
To Steve Correll,
Thank you for your advice, that's is right.
The first problem can be canceld by change -c++=pathcc to -c+
+=pathCC. But there are another error now when compile simpl.o as
follows:
/home/lxj/mpich/bin/mpicc -o simpleio simpleio.o
/home/lxj/mpich/lib/libmpich.a(_close.o)(.text+0x1b): In function
`MPI_File_close':
: undefined reference to `MPIO_File_resolve'
/home/lxj/mpich/lib/libmpich.a(_close.o)(.text+0x65): In function
`MPI_File_close':
: undefined reference to `MPIO_Err_create_code'
..
..
..
/home/lxj/mpich/lib/libmpich.a(_write.o)(.text+0xa05): In function
`MPIOI_File_write':
: undefined reference to `ADIO_ImmediateOpen'
collect2: ld returned 1 exit status
make[2]: *** [simpleio] Error 1
make[1]: *** [all] Error 2
rm -f *.o *~ PI* cpi pi3 simpleio hello++ pi3f90 cpilog
rm -rf SunWS_cache ii_files pi3f90.f pi3p cpip *.ti *.ii
installed MPICH in /home/lxj/mpich
Wish you can help me about the problem. Thank you.
For the second problem I mentioned yesterday, it is cause by my
script. In my script it will compile all fortran files, but some
files whether to be compiled depends the option of SUBTYPE, so it
cause the problem. Thank you for your advice Steve Correl.
.
- Follow-Ups:
- Re: a problem about NPB MPI benchmark , pathscale：pathf90
- From: Steven Correll
- Re: a problem about NPB MPI benchmark , pathscale：pathf90
- References:
- a problem about NPB MPI benchmark , pathscale：pathf90
- From: kinglu
- Re: a problem about NPB MPI benchmark , pathscale：pathf90
- From: Steven Correll
- a problem about NPB MPI benchmark , pathscale：pathf90
- Prev by Date: [ANN] Data Plotting Library DISLIN 9.4
- Next by Date: alternative to pause
- Previous by thread: Re: a problem about NPB MPI benchmark , pathscale：pathf90
- Next by thread: Re: a problem about NPB MPI benchmark , pathscale：pathf90
- Index(es):
Relevant Pages
|
