Re: [Libmesh-devel] Automake merge complete

2012-11-16 Thread Derek Gaston
So, did we decide we were going to check in "configure" or what? Here's what happens with bootstrap on my Lion MacBook Pro: autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal -I m4 configure.ac:56: error: Autoconf version 2.62 or higher is

[Libmesh-devel] Automake merge complete

2012-11-16 Thread Kirk, Benjamin (JSC-EG311)
Merge is complete and trunk is back in business. I'll be working on updating documentation for updating the build system over the next few days. In the meantime please contact me before you get too frustrated with automake - it is usually easy to do something if you do it the 'automake way.' -

[Libmesh-devel] Automake merge in progress - do not commit!

2012-11-16 Thread Kirk, Benjamin (JSC-EG311)
As of r6384, I am merging the automake branch back in to trunk. The old build system (trunk at r6383) exists as https://libmesh.svn.sourceforge.net/svnroot/libmesh/branches/libmesh-0.8.0 Unfortunately, the underlying SVN database on sourceforge is old and crusty, so am having to do some svn

Re: [Libmesh-devel] libmesh.automake merge

2012-11-16 Thread Kirk, Benjamin (JSC-EG311)
OK. doing it now, will send a summary email describing the changes within the hour. -Ben On Nov 16, 2012, at 3:08 PM, Roy Stogner wrote: > > On Fri, 16 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote: > >> Actually looks like I have some free time now - anything else in the >> pipeline? > > Hm

Re: [Libmesh-devel] libmesh.automake merge

2012-11-16 Thread Roy Stogner
On Fri, 16 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote: > Actually looks like I have some free time now - anything else in the pipeline? Hmmm... the remaining steps to get Cygwin working (new versions of Cygwin, anyway - their shared library conventions seem to have changed slightly in the last s

Re: [Libmesh-devel] libmesh.automake merge

2012-11-16 Thread Kirk, Benjamin (JSC-EG311)
Actually looks like I have some free time now - anything else in the pipeline? -Ben On Nov 16, 2012, at 12:37 PM, "Kirk, Benjamin (JSC-EG311)" wrote: > Thanks. I won't do this until the evening at the earliest. > > -Ben > > > > On Nov 16, 2012, at 12:17 PM, "Roy Stogner" wrote: > >> On

[Libmesh-devel] Patch for storing solution histories in memory

2012-11-16 Thread Vikram Garg
Hey all, This is the first and hopefully hardest step towards getting time-dependent adjoints support going. The patch attached will enable the user to save and retrieve solutions at all timesteps. The user will do this by declaring a MemorySolutionHistory object and then passing a refe

Re: [Libmesh-devel] libmesh.automake merge

2012-11-16 Thread Kirk, Benjamin (JSC-EG311)
Thanks. I won't do this until the evening at the earliest. -Ben On Nov 16, 2012, at 12:17 PM, "Roy Stogner" wrote: > On Fri, 16 Nov 2012, Roy Stogner wrote: > >>> There might be another ParallelMesh-with-repartitioning fix coming >>> soon, but nothing from me that should prevent the fork /

Re: [Libmesh-devel] libmesh.automake merge

2012-11-16 Thread Roy Stogner
On Fri, 16 Nov 2012, Roy Stogner wrote: >> There might be another ParallelMesh-with-repartitioning fix coming >> soon, but nothing from me that should prevent the fork / merge. Actually, I'll have a few Cygwin fixes coming in too. I'll check for branched-out-from-under-me before committing them,

Re: [Libmesh-devel] libmesh.automake merge

2012-11-16 Thread Roy Stogner
forgot to copy to list On Fri, 16 Nov 2012, Roy Stogner wrote: > > On Fri, 16 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote: > >> are there any outstanding uncommitted changes on trunk I need to hold off >> for? > > There might be another ParallelMesh-with-repartitioning fix coming > soon, but not

Re: [Libmesh-devel] Icosasphere mesh generation

2012-11-16 Thread Roman Vetter
Great, thanks! Roman Am 2012-11-16 16:08 , schrieb Kirk, Benjamin (JSC-EG311): > On Nov 16, 2012, at 2:38 AM, Roman Vetter wrote: > >> Dear libMesh developers, >> >> I would like to propose the attached patch (against r6373) for the >> trunk. It reflects the fact that the term "two-dimensional

[Libmesh-devel] libmesh.automake merge

2012-11-16 Thread Kirk, Benjamin (JSC-EG311)
All - I'd like to merge the automake branch. My plan is (1) copy the current trunk to branches/libmesh-0.8.0 in case anything else needs to be resolved for that release feature (2) merge the libmesh.automake branch back to trunk are there any outstanding uncommitted changes on trunk I need to

Re: [Libmesh-devel] Icosasphere mesh generation

2012-11-16 Thread Kirk, Benjamin (JSC-EG311)
On Nov 16, 2012, at 2:38 AM, Roman Vetter wrote: > Dear libMesh developers, > > I would like to propose the attached patch (against r6373) for the > trunk. It reflects the fact that the term "two-dimensional sphere in > three-dimensional space" is ambiguous: It could be a flat disk, or a > hollo

[Libmesh-devel] Icosasphere mesh generation

2012-11-16 Thread Roman Vetter
Dear libMesh developers, I would like to propose the attached patch (against r6373) for the trunk. It reflects the fact that the term "two-dimensional sphere in three-dimensional space" is ambiguous: It could be a flat disk, or a hollow sphere. Both topologies are very relevant in practice, but on