:)
The other library i'm using is an image processing library ITK. I compile each library with it's own respective build system. I've seen problems at compile time and runtime. The interface code that uses both libmesh and ITK is giving me the problems. The compiler options used by libMesh in debug mode >> -ansi -pedantic -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC seem to conflict with ITK. works w/ intel compilers. So I just want to change the gcc compile options in libMesh debug mode. >> -ansi -pedantic -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC seem to be calling some special stl debugging libraries that are giving me problems. thanks very much for the quick reply john, df On Thu, 18 Dec 2008, John Peterson wrote: > On Thu, Dec 18, 2008 at 10:09 AM, David Fuentes <[email protected]> wrote: >> >> >> Working with gcc 4.3.1 in debug mode, the compiler options >> >> >> -ansi -pedantic -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC >> >> >> >> chosen by the configure script do not seem to play nice with another >> library I'm using. Aside from hacking the configure file, what >> would be the best way to remove these options when compiling libMesh >> in debug mode ? > > Hmm... I guess it depends on the problem. Is it at compile time, run > time, or link time? > > If you are using libmesh's compiler flags to compile another library > then I guess the answer would be "don't do that" :-) > > -- > John > ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
