On Thu, Nov 8, 2012 at 12:19 PM, Roy Stogner <royst...@ices.utexas.edu>wrote:
> Have you tried setting options "in between" the opt and debug flags by
> hand? That's was the (successful) last hope for me when such a
> heisenbug hit once - try to figure out whether the breakage is due to
> the optimization flags or the removed libstdcxx debugging flags or
> what.
>
Well... on the automake branch I don't believe you get any of those
libstdcxx debugging flags, even when METHOD=dbg. Here's a sample
compilation line from 'make V=1':
/bin/sh ./libtool \
--tag=CXX \
--mode=compile \
mpicxx -DHAVE_CONFIG_H \
-DDEBUG \
-DLIBMESH_IS_COMPILING_ITSELF \
(various -I paths) \
-O0 \
-felide-constructors \
-g \
-ansi \
-pedantic \
-W -Wall -Wextra -Wno-long-long \
-Wunused -Wpointer-arith -Wformat \
-Wparentheses -std=c++0x -Woverloaded-virtual \
-fopenmp \
-MT \
src/utils/utility.lo \
-MD -MP -MF $depbase.Tpo \
-c -o src/utils/utility.lo \
src/utils/utility.C
Mostly warning stuff going on here. Any of these strike you as something
to try removing?
Side question: what's the right way to manually edit compiler flags on the
automake branch? Looks like I can edit the generated Makefile directly...
--
John
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
