On Mon, 3 Sep 2012, Ataollah Mesgarnejad wrote: > http://stackoverflow.com/questions/6112362/explicit-instantiation-of-a-templated-class-and-dynamic-cast-in-a-shared-library > > way over my head here but I think the second answer is the key.
This is interesting. I think the discussion of the C++ standard is wrong, though. C++ leaves shared library behavior "undefined" only in the same way it doesn't define behavior on Intel processors or behavior on Windows XP; some things (e.g. what happens when dereferencing NULL or reading past the end of an array) are implementation-dependent, but most of the standard is still supposed to be followed. That includes dynamic_cast; nothing in 5.2.7 suggests otherwise, and grepping through the other thousand pages of the standards draft didn't come up with anything either. But whatever. Do either of the compiler/linker flags here help? http://www.personal.psu.edu/stm134/Software.html Alternatively, try commenting out the HAVE_RTTI definition in libmesh_config.h - do things then work? --- 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
