>> >> 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 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! :-) 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. Glad to hear you are not opposed to this option! -Ben ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
