Not sure if this an option you want, but it's probably worth mentioning: should we have configure test for when templated casts are broken across dynamic library boundaries, and then turn off LIBMESH_HAVE_RTTI whenever that's the case? Internal to the library we're fine falling back on the static_cast code paths, so this would at least be a big help to new users on new OS X versions.
What do you guys need Fortran support for? PETSc third-party libraries? In-house code? --- Roy ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
