LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Brian Barrett (brbarret_at_[hidden])
Date: 2005-05-09 08:36:01


On May 9, 2005, at 6:17 AM, Christophe Peyret wrote:

> Rather than reconfiguring and building lam-mpi on MacOSX Tiger, I
> have copied the directory /Previous System/.../usr/local/lam-7.1.1
> as /usr/lam-7.1.1.
>
> This way lamboot and other lam commands work but I am still unabble
> to comile my program, it returns me the message :
>
> xlf_r -framework Accelerate -qsmp=omp ./obj/etime.o ./obj/
> Config.o ./obj/Config_static.o ./obj/Medium.o ./obj/
> Medium_Static.o ./obj/Duct.o ./obj/Duct_Static.o ./obj/Wave.o ./obj/
> Wave_Static.o ./obj/Point.o ./obj/Point_Static.o ./obj/Side.o ./obj/
> Side_Static.o ./obj/Mode2D.o ./obj/ModeAxi.o ./obj/Source.o ./obj/
> Source_Static.o ./obj/ElL2.o ./obj/ElT3.o ./obj/ElT4.o ./obj/
> Element.o ./obj/Element_Static.o ./obj/Vector.o ./obj/Matrix.o ./
> obj/Mesh.o ./obj/Init.o ./obj/Driver_Euler_Inst_C.o ./obj/
> Driver_Euler_Inst_R.o ./obj/Driver_Euler_Harm.o -L../blas/lib -
> lblas -L../LAPACK -llapack -L../LAPACK95 -llapack95 -L../
> arpack -larpack_MACOSX -L../ARPACK -lparpack_MPI-MACOSX -
> L../bessel/lib -lbessel -L../ode/lib -lode -L../solver/lib -
> lsolver -L../metis -lmetis -L/usr/local/lam-7.1.1/lib -
> llammpio -llamf77mpi -lmpi -llam -ldl -pthread -
> qextname=lam_darwin_malloc_linker_hack -force_flat_namespace -
> flat_namespace -Wl,-multiply_defined -Wl,suppress -o ./lamspace
> ld: Undefined symbols:
> _printf$LDBLStub
> _fprintf$LDBLStub
> _sprintf$LDBLStub
> _vsprintf$LDBLStub
>

That looks like there is something fundamentally wrong with your
installation of the XL compilers. Unfortunately, we can't offer much
assistance with your compiler -- you should contact either IBM (if
you bought it directly from them) or Absoft. Either should be able
to get you configured correctly or let you know how long it will be
until the compilers get updated to work with Tiger. By the way, your
other e-mail was caused by the same problem - your compiler was
unable to build a simple C program, so our configure script refused
to continue.

Brian