[Libmesh-devel] Warning after recent change in xdr?

2013-11-18 Thread John Peterson
Not really sure what the context for the change originally was... just wanted to raise the issue here. ../src/mesh/xdr_io.C: In instantiation of 'void libMesh::XdrIO::read_serialized_connectivity(libMesh::Xdr&, libMesh::dof_id_type, std::vector&, T) [with T = long long unsigned int; libMesh::dof_i

Re: [Libmesh-devel] Warning after recent change in xdr?

2013-11-18 Thread Roy Stogner
On Mon, 18 Nov 2013, John Peterson wrote: > Not really sure what the context for the change originally was... Fixing a crash when reading 4-byte files into 8-byte libMesh builds. Didn't realize I was just creating the same bug in the reversed case. I think I've got a fix for both cases figured

Re: [Libmesh-devel] Warning after recent change in xdr?

2013-11-18 Thread Cody Permann
Go ahead - I'm at SC and probably won't be sitting here much longer... Plus I'm on an underpowered laptop. Thanks! Cody On Mon, Nov 18, 2013 at 5:03 PM, Roy Stogner wrote: > > On Mon, 18 Nov 2013, John Peterson wrote: > > > Not really sure what the context for the change originally was... > > F

Re: [Libmesh-devel] SILO Support in libMesh

2013-11-18 Thread Derek Gaston
I, for one, vote to treat it just like Exodus... I don't like having to go install something separately for mesh file formats Derek On Mon, Nov 18, 2013 at 3:08 PM, Miller, Mark C. wrote: > I hadn't seen this thread. > > Download: silo.llnl.gov/Downloads > > There are two variants of each

Re: [Libmesh-devel] SILO Support in libMesh

2013-11-18 Thread Roy Stogner
On Mon, 18 Nov 2013, Derek Gaston wrote: > I, for one, vote to treat it just like Exodus... I don't like having > to go install something separately for mesh file formats In the long run I'd prefer more granularity in how we pull in third party libraries (Exodus included); in the short run I