On Thu, Oct 4, 2012 at 3:28 PM, Cody Permann <codyperm...@gmail.com> wrote:
> So I went through the process of updating Fparser today (Version 4.3.3 ->
> 4.5) in an attempt to figure out why our compiler stack wouldn't compile it
> in debug mode. I have successfully tested this update on Linux/GNU, OS
> X/Apple-GCC, and OS X/Clang without any issues. It's a somewhat
> painstaking process since the Makefile in libMesh was extensively modified
> but I believe that I have preserved all of the existing behavior properly.
> On a side note, I still can't compile it in debug mode but that's besides
> the point.
... and in other news - we finally located the cause of the problem with my
debug builds earlier today. Somehow our tech managed to provide a bad
configure line to Petsc that only corrupted the ability of my compiler to
produce a working debug build of libMesh. I know this doesn't make sense
but he was able to reconfigure/rebuild Petsc and the problem magically
disappeared in libMesh. One of those truly, "WTH" moments...
Oh well, I guess if the fparser patch goes in, at least I accomplished
something...
>
> The patch is way to big to attach here, but are there any comments before
> I commit to trunk?
>
> Thanks,
> Cody
>
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
