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"
<[email protected]<mailto:[email protected]>> wrote:
Didn't CC the list...
---------- Forwarded message ----------
From: Derek Gaston <[email protected]<mailto:[email protected]>>
Date: Tue, Feb 12, 2013 at 12:27 PM
Subject: Re: [Libmesh-devel] Build Error
To: "Kirk, Benjamin (JSC-EG311)"
<[email protected]<mailto:[email protected]>>
On Tue, Feb 12, 2013 at 12:24 PM, Kirk, Benjamin (JSC-EG311)
<[email protected]<mailto:[email protected]>> wrote:
This happens when HDF5 is not properly found, disabling netcdf4, but exodusII
is still looking for that symbol
I tried just --disable-hdf5 and that didn't do it either.
Also - it's "--enable-netcdf=old" right? Not "with"? Or do both work?
I can verify that turning everything (nemesis, netcdf, exodus) back to old
_does_ still work. But is kind of a bummer ;-)
Going forward it looks like we (the MOOSE team) should distribute HDF5 to our
users....
Derek
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Libmesh-devel mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
