[Libmesh-devel] Build Error

2013-02-12 Thread Derek Gaston
Guys, we're seeing a build error with the new netcdf on Linux: CXXLDgetpot_parse-opt ./.libs/libmesh_opt.so: undefined reference to `nc_def_var_deflate' collect2: ld returned 1 exit status make[1]: *** [getpot_parse-opt] Error 1 make[1]: Leaving directory `/home/gastdr/projects/herd_trunk/li

Re: [Libmesh-devel] Build Error

2013-02-12 Thread Derek Gaston
This is consistent across multiple different distros and architectures... you guys gotta be seeing this, right? We're looking for a fix now... Derek On Tue, Feb 12, 2013 at 11:58 AM, Derek Gaston wrote: > Guys, we're seeing a build error with the new netcdf on Linux: > > CXXLDgetpot_par

Re: [Libmesh-devel] Build Error

2013-02-12 Thread Kirk, Benjamin (JSC-EG311)
Yep, I'm on it. This happens when HDF5 is not properly found, disabling netcdf4, but exodusII is still looking for that symbol. You can get the old stuff back with $ ./configure --with-netcdf=old --with-exodus=old --with-nemesis=old but I should have it fixed shortly. -Ben On Feb 12, 2013,

[Libmesh-devel] Fwd: Build Error

2013-02-12 Thread Derek Gaston
Didn't CC the list... -- Forwarded message -- From: Derek Gaston Date: Tue, Feb 12, 2013 at 12:27 PM Subject: Re: [Libmesh-devel] Build Error To: "Kirk, Benjamin (JSC-EG311)" On Tue, Feb 12, 2013 at 12:24 PM, Kirk, Benjamin (JSC-EG311) < benjamin.kir...@nasa.gov> wrote: > This

Re: [Libmesh-devel] Fwd: Build Error

2013-02-12 Thread Kirk, Benjamin (JSC-EG311)
I think it is possible to use the new exodus even with the netcdf4 symbols missing, but I'm not sure yet what aspect of the new functionality will be reduced. -Ben On Feb 12, 2013, at 1:28 PM, "Derek Gaston" mailto:fried...@gmail.com>> wrote: Didn't CC the list... -- Forwarded mess

Re: [Libmesh-devel] Fwd: Build Error

2013-02-12 Thread Derek Gaston
Ok - we'll just stick to the old stuff for now until we can distribute HDF5. Derek On Tue, Feb 12, 2013 at 12:55 PM, Kirk, Benjamin (JSC-EG311) < benjamin.kir...@nasa.gov> wrote: > I think it is possible to use the new exodus even with the netcdf4 symbols > missing, but I'm not sure yet what as

Re: [Libmesh-devel] Fwd: Build Error

2013-02-12 Thread Cody Permann
Here's another "new" error when using the new contribs: Exodus Library Error: [ex_put_block] Error: failed to define number of nodes/entity for element block 507 in file id 131072 [-41] netcdf constraint NC_MAX_DIMS exceeded Error writing element block. Stack frames: 14 0: 0 libmesh_dbg.0.dyli

Re: [Libmesh-devel] Fwd: Build Error

2013-02-12 Thread Kirk, Benjamin (JSC-EG311)
On Feb 12, 2013, at 2:13 PM, Cody Permann wrote: > We have a number of tests that have started failing that use several hundred > subdomains. I haven't dived into this at all yet, but on the surface it > looks like we might need to call additional API functions or something in our > ExodusII

Re: [Libmesh-devel] Fwd: Build Error

2013-02-12 Thread Cody Permann
On Tue, Feb 12, 2013 at 1:23 PM, Kirk, Benjamin (JSC-EG311) < benjamin.kir...@nasa.gov> wrote: > > On Feb 12, 2013, at 2:13 PM, Cody Permann wrote: > > > We have a number of tests that have started failing that use several > hundred subdomains. I haven't dived into this at all yet, but on the >

Re: [Libmesh-devel] Fwd: Build Error

2013-02-12 Thread Kirk, Benjamin (JSC-EG311)
On Feb 12, 2013, at 2:49 PM, Cody Permann wrote: > > I need to increase some parameter bounds in netcdf - I'm doing that and will > commit a fix if it still works. > > Excellent! > Cody It is in as of 4695b094f00c1076be21241050942414a2f22ac2 -Ben --