On Thu, 17 May 2012, Andrew E Slaughter wrote: > Is there something different with respect to include and link > directories between a dbg and opt build? I have it working with libmesh > in opt, but it provides the error when I switch to dbg.
There's no difference with include directories; the link directory definitely should differ, though. In fact, libmesh.so generated with METHOD=dbg can be binary *incompatible* with application object files generated with any other method. METHOD=dbg tries to define the GLIBCXX_DEBUG macros if appropriate (I forget whether we turn this on only for gcc or for other compilers too), which tells GNU libstdc++ to use a slower-but-more-error-checked version of the STL containers. The debug std::vector isn't binary compatible with (or even given the same underlying symbol name as) the optimized std::vector, so if you mixed up the link directories then this might cause the linker failures you saw: missing function signatures for functions taking arguments of one vector type or the other. --- Roy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
