All,
libMesh-0.9.0 now available:
https://sourceforge.net/projects/libmesh/files/libmesh/libmesh-0.9.0
Some of the major changes include
0.8.0 -> 0.9.0
* automake build system
libMesh-specific implementation features:
source and header files must be listed explicitly.
When adding
Ben,
What hash did you actually take it from? Are you actually going to publish
that branch on GitHub as well?
Derek
On Wed, Feb 6, 2013 at 10:16 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> All,
>
> libMesh-0.9.0 now available:
> https://sourceforge.net/projects/libmes
On Feb 6, 2013, at 11:41 AM, Derek Gaston wrote:
> Ben,
>
> What hash did you actually take it from? Are you actually going to publish
> that branch on GitHub as well?
>
> Derek
I pushed a tag to GitHub - there is no branch associated with it (yet).
hash is 0dd148f5164131ea6bea45e15a87f1695d
That's great with me. I just wanted to know which one was "gold" ;-)
On Wed, Feb 6, 2013 at 12:48 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> On Feb 6, 2013, at 11:41 AM, Derek Gaston wrote:
>
> > Ben,
> >
> > What hash did you actually take it from? Are you actually g
On Wed, Feb 6, 2013 at 1:48 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
>
> I figured I'd start a branch from that tag if anything needed fixing… got
> a better plan?
>
I'm still a git noob so forgive my ignorance, but what about tagging the
version number?
http://git-scm.
On Wed, Feb 6, 2013 at 12:52 PM, Paul T. Bauman wrote:
> On Wed, Feb 6, 2013 at 1:48 PM, Kirk, Benjamin (JSC-EG311)
> wrote:
>>
>>
>> I figured I'd start a branch from that tag if anything needed fixing… got
>> a better plan?
>
>
> I'm still a git noob so forgive my ignorance, but what about tag
On Feb 6, 2013, at 11:52 AM, "Paul T. Bauman" wrote:
> On Wed, Feb 6, 2013 at 1:48 PM, Kirk, Benjamin (JSC-EG311)
> wrote:
>
> I figured I'd start a branch from that tag if anything needed fixing… got a
> better plan?
>
> I'm still a git noob so forgive my ignorance, but what about tagging
On Wed, Feb 6, 2013 at 1:59 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
>
> elfboy(142)$ git tag
> v0.9.0
> v0.9.0-rc1
>
> you may need to do a 'git pull --tags' to get it in your local copy?
Oh dammit, there it is. Sorry for the noise.
-
It looks like the libMesh configure ends up running the netcdf v4
configure, passing our relevant options and environment variables to
it... but *without* properly escaping any spaces first, so that
'CC="distcc gcc"' becomes '"CC=distcc" gcc'.
I can't yet actually find anything wrong in our autot
On Feb 6, 2013, at 1:35 PM, Roy Stogner wrote:
> I can't yet actually find anything wrong in our autotools scripts that
> would be causing this, but I can't believe that the bug is in autoconf
> itself... that whole system relies on shell scripting so paranoid that
> it eschews every little non-P
On Wed, 6 Feb 2013, Kirk, Benjamin (JSC-EG311) wrote:
> What I am trying to accomplish is to force netcdf to use our
> compilers. Without this it''l happily go and find its own,
> regardless of what we are using. note that this is not strictly a
> problem but seems silly to me.
Oh, that would
On Feb 6, 2013, at 1:56 PM, Roy Stogner wrote:
>>
>> What I am trying to accomplish is to force netcdf to use our
>> compilers. Without this it''l happily go and find its own,
>> regardless of what we are using. note that this is not strictly a
>> problem but seems silly to me.
>
> Oh, that w
12 matches
Mail list logo
