On Fri, 13 May 2011, Kirk, Benjamin (JSC-EG311) wrote:
> Perhaps we should just disable boost based on compiler version? I have not
> done that yet.
Yeah; unless we set up some regression tests with various compilers
(inconvenient, unless we restrict ourselves to gcc versions) I guess
we just
>> BTW, how do we compile the new contrib/boost/test_boost.C?
>
/usr/bin/g++ -o test_boost test_boost.C -I $LIBMESH_ROOT/contrib
I was just trying to make sure I had all the dependencies needed for the
files included in test_boost.C...
> And do we have and/or need any fallbacks for older compile
On Fri, 13 May 2011, John Peterson wrote:
> https://sourceforge.net/mailarchive/forum.php?thread_name=c2d912840808111520u6ea7e276nfd30609fb550%40mail.gmail.com&forum_name=libmesh-devel
>
> BTW, how do we compile the new contrib/boost/test_boost.C?
And do we have and/or need any fallbacks for
On Thu, May 12, 2011 at 12:41 PM, Kirk, Benjamin (JSC-EG311)
wrote:
> I have just committed a change to the DofObject with completely restructures
> its internal storage. It is now using a contiguous buffer for all index
> information. I think this is something John wanted me to do about 5 years
> Very nice!
>
> I hope you got started on this because of the ParallelMesh work, not
> because you were running into the same out-of-memory errors that were
> killing Paul and I in FIN-S? It turned out that the root problem was
> a memory leak in libablation svn trunk, now fixed there and in 0.
Very nice!
I hope you got started on this because of the ParallelMesh work, not
because you were running into the same out-of-memory errors that were
killing Paul and I in FIN-S? It turned out that the root problem was
a memory leak in libablation svn trunk, now fixed there and in 0.25.0.
Any n
