At 01:20 AM 12/4/2004, Kamaraju Kusumanchi wrote:
>On Fri, 03 Dec 2004 20:04:54 -0600, Ryuta Suzuki <suzu0037_at_[hidden]> wrote:
> > You need to set
> >
> > call MPI_Finalize(ierror)
>
>
>thank you very much for the reply. That solved the problem. However I
>have one more question. This time I am trying to build lam-mpi with
>ifort 8.1, icc 8.1 using the following options (building static
>libraries).
>
>export FC=ifort
>export CC=icc
>export CXX=icpc
>export FFLAGS=""
>export CFLAGS="-cxxlib-icc -static"
>export CXXFLAGS="-cxxlib-icc -static"
>
>After compiling the lam-mpi libraries with the above options.
>
>If I try to run
>mpif77 -static helloworld.f90
>I get the following warnings. Is there any to avoid these errors?
>
>/data/raju/kusumanchi_rajulocal/software/compiledLibs/lammpi_icc81_ifort81_corrsin/lib/liblam.a(ltdl.o)(.text+0x2ed):
>In function `sys_dl_open':
>: warning: Using 'dlopen' in statically linked applications requires
>at runtimethe shared libraries from the glibc version used for linking
>/opt/intel_fc_80/lib/libifcoremt.a(for_open_proc.o)(.text+0x37dc): In
>function `for__compute_filename':
>: warning: Using 'getpwnam' in statically linked applications requires
>at runtime the shared libraries from the glibc version used for
>linking
>/data/raju/kusumanchi_rajulocal/software/compiledLibs/lammpi_icc81_ifort81_corrsin/lib/liblam.a(kill.o)(.text+0x62):
>In function `lam_tmpdir_init_opt':
>: warning: Using 'getpwuid' in statically linked applications requires
>at runtime the shared libraries from the glibc version used for
>linking
>/data/raju/kusumanchi_rajulocal/software/compiledLibs/lammpi_icc81_ifort81_corrsin/lib/liblam.a(lam_gethostby.o)(.text+0x19):
>In function `lam_gethostbyaddr':
>: warning: Using 'gethostbyaddr' in statically linked applications
>requires at runtime the shared libraries from the glibc version used
>for linking
>/data/raju/kusumanchi_rajulocal/software/compiledLibs/lammpi_icc81_ifort81_corrsin/lib/liblam.a(lam_gethostby.o)(.text+0x5):
>In function `lam_gethostbyname':
>: warning: Using 'gethostbyname' in statically linked applications
>requires at runtime the shared libraries from the glibc version used
>for linking
This is a common problem, annoying enough that you should consider filing a
report on your premier.intel.com account. You could check your build with
nm and ldd to see whether those functions are in fact linked
dynamically. We have found in one case that we could correct the problem
by capturing the ld command line (mpif77 -# ....) and altering it. For
example, using mpicc (built with gcc), or gcc with the addition of the lam
and ifort libraries, or even icc used similarly, might be found to pass a
more favorable command line to ld. Also, if the warnings still come out
when you omit -static, you might put that forward as additional
evidence. If mpif77 without -static avoids the problem, capturing that ld
command might give a clue what should be changed in the static link. If
you file a problem report, I expect you will need to attach the lam
libraries which are used in your link, at least those which show up in the
-# report, and those which ldd shows are required to run. Evidently, you
will also need to tell whether you have a run time problem; if so, could
you fix it by altering the ld command line, and could you determine the
nature and location of the problem by running under debugger. In our
recent case, it dies under mpich with a segfault in gethostbyname() (which
is static linked, in spite of the message saying it is not), but it runs OK
under lam-6.5.9 and 7.0.3. As you can show the problem in "hello world,"
that would be a good example to submit.
Tim Prince
|
