That's possibly it. I remember that getting commented out myself… and it was definitely for a compile issue, but I can't remember if it was exactly this issue.
Let me say this though: it doesn't need the optimizer stuff. I was just running benchmarks last night that heavily utilized FParser… and it doesn't even show up in profiling… like not even close. I propose just turning it off for now (or maybe just turning it off for macs). Derek On Jan 30, 2012, at 3:07 PM, John Peterson wrote: > On Mon, Jan 30, 2012 at 2:59 PM, Derek Gaston <fried...@gmail.com> wrote: >> What's weird to me is that we have fparser working fine in MOOSE. What's >> different about our version? Is this something that Phillip (the intern who >> put in the function parsing stuff) solved when he put fparser into MOOSE or >> is this something that has happened in the interim? > > The version in MOOSE has the optimizer stuff turned off (see fpconfig.h). > > The entire optimize_main.cc file is #ifdef'd out in this case, > therefore you don't get the duplicate macro call. > > Cody seems to remember them commenting out the optimizer stuff a ways > back for some reason, but couldn't remember exactly what. Maybe this > is it? > > -- > John ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
