Hi Li,

(Other developers please feel free to chime in)

On Wed, May 25, 2016 at 8:41 PM, <li....@siat.ac.cn> wrote:
>
>
> 1, How can I configure a debugging version of libmesh? It seems there is
> not such an option when configure -h,  I added "--with-debugging=yes" to
> the configure command as I did for PETSc, it seems that this can generate a
> debug verion of libmesh, but I am not sure.
>

Setting the environment variable (or on the configure line) METHOD=devel
will turn on asserts and debugging flags, but will still have -O2.
METHOD=dbg will use -O0 and some other debugging flags. I use METHOD=devel
the vast majority of the time. Only occasionally do I need to use
METHOD=dbg.


> 2, It outputs an error when I install libmesh: "attempted static link with
> libstdc++.so", how can I link this lib correctly?
> It seems that adding "--enable-shared" does not work.
>

You can use --disable-static to turn off static linking, but we should be
using dynamic linking by default. What system are you running on? Are you
sure that it supports dynamic linking? IIRC, some environment like Cray (I
won't swear to this) didn't support shared linking?


> Currently I just delete libstdc++.so and add "-lstdc++", but too many
> objects need to link with this lib, can I handle this by changing something
> in configure or Makefile?
>
> 3, I configure with the following options, for the particularity of our
> machine, I deleted libstdc++.so and add "-lstdc++", and remove "-lgcc_s"
> when linking, the ex2 in examples/systems_of_equations outputs error:
> ***Memory allocation for gkmcore failed.
>
> This error occurs in Build_square(); I have debug it with gdb, as shown in
> the attached file "gdb_output.txt".
>
> My configure options are:
> ./configure \
>     CC=mpicc FC=mpif90 CXX=mpiCC AR=swar RANLIB=swranlib \
>

Why are you needing to specify AR and RANLIB?


>
> --prefix=/home/export/online1/systest/swsiat/luoli/libmesh-0.9.3/install-debug
> \
>     --enable-shared \
>     --enable-blocked-storage \
>     --enable-perflog \
>     --enable-parmesh \
>     --with-debugging=yes \
>     --with-dof-id-bytes=8 \
>     --host=alpha \
>     --disable-gzstreams \
>     --disable-tetgen \
>     --disable-eigen \
>     --disable-fparser \
>     --disable-libHilbert \
>     --disable-nanoflann \
>     --disable-sfcurves \
>     --disable-gmv \
>     --disable-nemesis \
>     --disable-laspack \
>     --disable-triangle \
>     --disable-tbb
>
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to