On Sat, Oct 20, 2012 at 9:56 AM, Kirk, Benjamin (JSC-EG311) <email@example.com>
>> I'll double check with the latest port of everything, although I do think a lot of this is self imposed - why don't we use the released fparser package?
>> The development version uses yacc and makes a *lot* of assumptions about the compiler!I'll let Roy weigh in, but my observation has been that 90% of the current build requirements are to make the source compressor/obfuscator that in the end produces a single source file… and a lot of the compiler issues I've seen are with actually the compressor, not fparser itself.
> I completely agree! We used the release version in MOOSE for a long time before there was interest in including it in libMesh. If for no other reason than to cut 15 seconds off the build time! :-)
Roy, any thoughts on this or are we crazy here at the INL? I'm willing to prepare a patch to go back to the release version of the package or perhaps we could do something in between. Maybe "--enable-fparser-devel" and have it default to disabled bringing in only the release files for normal builds.
Glad to hear you are not opposed to this option!