Yes, it builds a static lib. I guess I could have also added
"--with-shared-libraries=0", just to be sure. Anyway I have that option in
my "production" installation of PETSc (among other flags related to third
party libraries, which I temporarily disabled to keep things as simple as
possible), but libMesh build fails with the same error.
On Sat, Nov 2, 2013 at 2:58 PM, John Peterson <jwpeter...@gmail.com> wrote:
>
>
> > On Nov 2, 2013, at 5:13 AM, Francesco Ballarin <
> francesco.balla...@polimi.it> wrote:
> >
> > Hi John,
> > thanks.
> >
> > a) I tried building PETSc with --with-clanguage=cxx as you suggested, my
> configure options are now
> > ===
> > ./configure --with-mpi-dir=/bgsys/drivers/ppcfloor/comm/xl/
> --with-clanguage=cxx
> --with-blas-lapack-lib=/opt/ibmmath/essl/5.1/lib64/libesslbg.a
> --with-make-np=8 --prefix=$PETSC_INSTALL_DIR
> > ===
>
> By the way, does this build a static petsc lib? If you are using
> --enable-all-static with libmesh, you'll need a static petsc.
>
>
>
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
