On Thu, Oct 13, 2011 at 10:26 PM, Roy Stogner <[email protected]> wrote: > > On Thu, 13 Oct 2011, Jed Brown wrote: > >> fe_type = {.order = libMeshEnums::SECOND, .family = >> libMeshEnums::LAGRANGE} >> >> and the value 6 is returned from fe_xyz.C:931 by > > Here's your problem: the linker isn't calling the right function. > > It's a linker problem I've seen before, too, where for some reason the > XYZ instantiation gets triggered to handle a LAGRANGE call. I don't > remember exactly what caused it, though. Something about the fe_* > object files getting built or linked out of their usual order, maybe? > Try hunting the mailing list archives.
http://sourceforge.net/mailarchive/message.php?msg_id=27134833 > Note that I don't say it's a linker error: I'm pretty sure that Ben's > fancy template partial partial specialization tricks aren't actually > legal C++. Interesting, can you be more specific? If we are invoking some kind of undefined behavior that would be good to fix... -- John ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
