[mpich-discuss] How to build libmpe.so ?
Seifer Lin
seiferlin at gmail.com
Tue May 5 05:25:43 CDT 2009
Hi:
The .so is a wrapper of mpich2 functions.
MPE is used to output log files for debugging.
Now I just use -fPIC to compile MPE and link libmpe.a into a .so file.
Seifer
2009/5/5 Anthony Chan <chan at mcs.anl.gov>
>
> Seifer,
> ----- "Seifer Lin" <seiferlin at gmail.com> wrote:
>
>
> > Now I want to port this DLL to Linux as the .so file.
> > I try to build mpich with
> > ./configure --enable-sharedlibs=gcc --with-pm=smpd --with-pmi=smpd
> >
> > but I only find libmpich.so and libmpe.a.
> > How to build mpe as the .so (libmpe.so) ?
>
> MPE currently does not have shared library support yet.
> If you really need libmpe.so, you can build MPE as a standalone
> package for MPICH2 with CFLAGS set to -fPIC. You can then
> use the .o files (from libmpe.a) and build your own libmpe.so.
>
> To build typical MPI executable, you can mix libmpich.so and libmpe.a.
>
> > Without libmpe.so, I got the error when building my .so file.
>
> What .so file you are building that needs libmpe.so ?
>
> A.Chan
>
> >
> > /usr/bin/ld: ./mpich2-x64/src/mpe2/lib/libmpe.a(mpe_log.o):
> > relocation
> > R_X86_64_32 against `a local symbol' can not be used when making a
> > shared
> > object; recompile with -fPIC
> > ./mpich2-x64/src/mpe2/lib/libmpe.a: could not read symbols: Bad value
> > collect2: ld returned 1 exit status
> >
> >
> > regards,
> >
> > Seifer Lin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20090505/7b41c45e/attachment-0001.htm>
More information about the mpich-discuss
mailing list