[Libmesh-devel] Time to update our Exodus/Nemesis versions?

2013-01-30 Thread Roy Stogner
The version up on SourceForge seems to be using int64_t pretty universally; the one in our contrib/ is hard-coded for int. --- Roy -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Down

Re: [Libmesh-devel] Time to update our Exodus/Nemesis versions?

2013-01-30 Thread John Peterson
On Wed, Jan 30, 2013 at 2:57 PM, Roy Stogner wrote: > > The version up on SourceForge seems to be using int64_t pretty > universally; the one in our contrib/ is hard-coded for int. Ugh... do you have a lot of free time on your hands? It's something that definitely needs to be done... I can just

Re: [Libmesh-devel] Time to update our Exodus/Nemesis versions?

2013-01-30 Thread Kirk, Benjamin (JSC-EG311)
I just added a ticket for this, but after the next release unless there is some serious urgency…. On Jan 30, 2013, at 4:03 PM, John Peterson wrote: > On Wed, Jan 30, 2013 at 2:57 PM, Roy Stogner wrote: >> >> The version up on SourceForge seems to be using int64_t pretty >> universally; the

Re: [Libmesh-devel] Time to update our Exodus/Nemesis versions?

2013-01-30 Thread Roy Stogner
On Wed, 30 Jan 2013, Kirk, Benjamin (JSC-EG311) wrote: I just added a ticket for this, but after the next release unless there is some serious urgency…. No urgency at all; it definitely shouldn't hold up the release. Biggest thing that is holding up the release from my POV right now is that